Skip to content

Conversation

@henriquebremenkanp
Copy link
Contributor

Q A
Bug fix? Yes
New feature? No
BC breaks? No
Deprecations? No
Fixed tickets #896

@pdbreen
Copy link
Contributor

pdbreen commented Nov 23, 2016

Looks like it should fix the problem I saw - I'll give it a run tomorrow when I'm back at work.


// Copy shared dir files if they does not exist.
run("if [ -d $(echo {{release_path}}/$dir) ]; then cp -rn {{release_path}}/$dir $sharedPath; fi");
run("if [ -d $(echo {{release_path}}/$dir) ]; then cp -rn {{release_path}}/$dir $sharedPath/$parentDir; fi");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On second look - would I want anything copied from my release path into my shared storage once shared storage is established? Seems like possible risk of unwanted / unexpected overwrite if I happen to have placeholder in my release tree. For example, if my release tree contained a shell sqlite DB file that I want to be shared/retained across releases, this copy would always reset back to the release tree version.

Maybe the copy from release tree should only be if $sharedPath/$dir doesn't yet exist? Your prior ticket indicated this change was trying to repair a first time deploy issue.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nevermind - I now the the -n option on cp that prevents overwrite.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your prior ticket indicated this change was trying to repair a first time deploy issue.

This is true. And i think to add this later, and remove -n flag (#894).

@antonmedv antonmedv merged commit 9cd3ef9 into deployphp:master Nov 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants