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.

Sign up for GitHub

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

Jump to bottom

dev only deploy strategy #162

Open
lloiacono opened this issue Jun 6, 2017 · 3 comments
Open

dev only deploy strategy #162

lloiacono opened this issue Jun 6, 2017 · 3 comments

Comments

@lloiacono
Copy link

Is it possible to have a dev only deploy strategy. Currently I need to have copy for production and symlink for local development as deploy strategy.

Would be nice to have a section to specify a deploy strategy for development only
@JeroenBoersma
Copy link
Contributor

Maybe we should move the deploy strategy to a environment based setting. With a fallback to the composer setting, this way copy could be the default and symlink if given.

For now, just update your composer.json locally and run the script to re-deploy based on symlinks.

@JeroenBoersma
Copy link
Contributor

Second option would be if we could work something out with the ---no-dev strategy.
So, if --no-dev us another parameter than when --dev

@JeroenBoersma JeroenBoersma mentioned this issue Jun 6, 2017
Merged
@JeroenBoersma
Copy link
Contributor

This can be closed with latest release, just composer update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JeroenBoersma @lloiacono