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
Dockerize #69
Conversation
Strongly urge that we seek feedback on this from the Slack |
Not yet mentioned features:
|
You should
|
Yeah I think we should discuss this more. It's also maybe hard to get docker to work on Windows Home and even WSL? |
Yep, I'll try to get this working in WSL. If that works, I don't think we should let Windows Home's flaws hold us back (that's not to say there's other reasons we might not want to do this). The number of developers who lie at the intersection of "only have Windows Home" and "have a stubborn attachment to Windows Home and the Windows terminal" is very small. |
@leonm1 resolve conflicts? |
Just realized - should |
@leonm1 resolve conflicts so we can merge? |
Will do today
|
IMPORTANT:
I'm actually kinda worried about this - I think there's a lot of intersecting functionality that we need to watch out for. |
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Needs rebase |
I don't think rebasing this is worth the time and honestly, I'd rather work on this from square one. I'll consult what you've done but I don't think I'll directly use the code you've written. |
Breaking changes:
docker-compose up --build
to build and run the container (anddocker-compose up
on subsequent runs). The advantage of this setup is that it only requires one command and will always produce the same result on every platform.env
now stores three variables, as docker-compose is hardcoded to use this file and we cannot change that:client.env
now stores all the env vars for the application, and docker-compose injects them into the containers