Add and use new release_or_current_path #2486
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Awesome! Thanks for also fixed other recipes as well! Will release a new beta right now. |
Merged
isleshocky77
added a commit
to isleshocky77/deployer
that referenced
this pull request
Jan 16, 2023
Updating this task to use release_or_current_path (from deployphp#2486) will allow the writable task to be used outside of deployment
5 tasks
antonmedv
pushed a commit
that referenced
this pull request
Jan 16, 2023
Updating this task to use release_or_current_path (from #2486) will allow the writable task to be used outside of deployment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As discussed in PR #2485, This PR enables users to run tasks outside a deployment by providing a new
release_or_current_pathoption.This option will always return the
release_pathif it exists and fallback to thecurrent_pathif it doesn't.That way, outside of deployment, we can still run
dep my:taskand expect our task to be executed on the latest active release.This PR replaces the use of
release_pathwithrelease_or_current_pathin all the custom tasks of platform-specific recipes — like laravel, symfony, etc. It also replaces the use ofrelease_pathin thedeploy:vendortask, allowing users to runcomposer installon the current release if they need to.Let me know if there are other places that would benefit from this new path.
Let me know what you think. 🙂