Added lot of options for advanced deployment scenario #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These options are useful if you want to push source files and build project (or part of project):
EXCLUDE_FILES
- specify which files should not to be copied toTARGET_DIR
(usually source files, composer.json, etc. By default: .git)RSYNC_FLAGS
- specify rsync flags without modifying deploy.php (useful if yourTARGET_DIR
should keep certain owner:group, but rsync resets them)COMMANDS_BEFORE_RSYNC
- run certain commands underGIT_DIR
between pulling updates from remote repo and doing rsync (composer install
,webpack
, etc)COMMANDS_AFTER_RSYNC
- run certain commands underTARGET_DIR
after doing rsync (this can berm cache/*.php -f
for example)CLEANUP_WORK_TREE
- clean upGIT_DIR
repo work tree after running all custom commands, resetting it to clean state (set totrue
it if you wish intermediate files not to survive between builds, does not affectTARGET_DIR
content at all)All these new options do not affect older config files. If they are missing in config, new functionality will be just ignored or set to default values (like hardcoded in old deploy.php).