Closed outrunthewolf closed 2 years ago
:+1:
Sounds like an awesome idea to me. I have had 0 experience with Docker, have you or @marcqualie ?
What would be the main advantages? I like the idea, would be useful to have a use case for it though
A few scenarios:
Instead of building all of your dependencies by hand, setting up a stack, then composing Criterion, the Dockerfile will handle all this for you within the Docker container.
Thinking about it though, perhaps a Docker file should be a seperate repo, if you specifically want to pull the Docker container file, you probably don't want the rest of the repository as well
I'm not 100% sure on how it all works (regarding the separate repo) but it sounds like a pretty neat setup to me. I'd been toying with the idea of vagrant for the same purpose but I don't really like it, Docker seems like the way forward.
When I originally saw this I thought you meant using docker to run the tests in isolated instances, instead of installing all of the project's dependencies on your criterion box. Reckon that could also be achievable?
The workers should technically be able to run on any box right now (i'd need to test that), all you would need to do is use the MongoDB config details of the main Criterion box. So that would be a really cool setup too. Being able to deploy worker boxes with docker.
You could spawn and run docker containers automatically, you can mount folders/files from outside the container within, I suppose its definitely achievable. Quite a novel idea actually!
What are your thoughts on creating a Dockerfile for Criterion?
So a user could simply pull the Dockerfile, Docker would then install all dependencies for Criterion, run composer to pull in Criterion, and expose the application on a port automatically.
For those who want it of course, another way to get up and running quickly