-
Notifications
You must be signed in to change notification settings - Fork 40
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
Replace Vagrant with docker #1607
Conversation
I have added very basic documentation. @stopfstedt when you get a chance please test this setup on your linux machine. You need docker-compose and then running |
☔ The latest upstream changes (presumably ed70bc0) made this pull request unmergeable. Please resolve the merge conflicts. |
@jrjohnson this will need a rebase against master, thanks! |
d514dd1
to
e7804b6
Compare
e7804b6
to
46340c6
Compare
46340c6
to
2d62929
Compare
Better volume mapping, connected to demo db, chown necessary symfony write directories.
Hopefully fixes issues on windows systems which do not seems to respect the executable permission on the original file.
Passing true to these new environmental variables will put docker container into development mode.
46bd789
to
5051c56
Compare
Just puts the PHP source into an image that can be versioned easily along with the source.
Better sharing of logs and an nginx container that is simplified by removing the entrypoint chown stuff which is now done elsewhere.
These need to be setup so PHP can write here and php-fpm runs as nobody.
Our vagrant instance is old and the promise of deploying a vagrant environment to production has never materialized. Instead lets use docker-compose to do this.
Fixes #789, #790, #899
WIP needs: