Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change deploy-strategy on the fly #105

Open
razbakov opened this issue Apr 4, 2016 · 4 comments
Open

Change deploy-strategy on the fly #105

razbakov opened this issue Apr 4, 2016 · 4 comments

Comments

@razbakov
Copy link

razbakov commented Apr 4, 2016

i want for all environments to have copy strategy and only for dev to have symlink.
is it maybe possible to change strategy on the fly?

composer config extra.magento-deploystrategy "symlink"

this doesn't work for me.

or would be nice to have some command to deploy with different strategies, for example:

composer run-script redeploy symlink
@Flyingmana
Copy link
Contributor

first one does not work because it takes the config out of the composer.lock file, so the second one would probably be the best. I would do it analog to the redeploy command then, because we have more composer context there then in run-script I think

@TKlement
Copy link

This is exactly what I need, too.
Any progress or workaround to solve this strategy at the moment?

@Julime
Copy link

Julime commented Oct 17, 2017

+1

@Morgy93
Copy link

Morgy93 commented Oct 17, 2017

issue push

Sadly the script also doesn't recognize --dev so that

"magento-deploystrategy": "copy",
"magento-deploystrategy-dev": "symlink"

has no effect on redeploy.
Maybe that's a different approach instead of changing the deploy strategy on the fly.

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

No branches or pull requests

5 participants