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

workflow: no magento core files or dockerize-magento2 in project repo #21

Open
WileESpaghetti opened this issue Feb 17, 2017 · 0 comments

Comments

@WileESpaghetti
Copy link

For our git repositories, we like to only have the stuff that we've written or changed checked in. Everything else is pulled in via composer install when someone checks out the project.

I don't think you can do this with the way dockerize-magento2 currently works. It seems like it's only intended to be installed once when you start the project with your repository containing both magento core files and dockerize-magento2 files.

...So example scenario
We start the project.
The initial commit is a barebones composer.json with magento listed as a dependency and with dockerize-magento2 as a dependency. We also have a .gitignore with magento core files listed.

Our development MySQL has different credentials, so we update our .env file and check it in.

New developer starts the project
* They checkout the repo
* The run composer install to fetch magento core files

Currently when we do this the composer install overwrites our .env file and stuff in config/ with the dockerize-magento2 defaults

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

1 participant