up
up copied to clipboard
paulcsmith
Up makes it easier to start, build, and run Docker for local development
This is in my up.yml ``` main_container: lucky docker_compose_command: docker-compose -f Docker/docker-compose.yml -f Docker/docker-compose.dev.yml ``` So I expected up run -e LUCKY_ENV=test lucky db.create To resolve to docker-compose -f Docker/docker-compose.yml...
If you're using a docker-compose version > 2, then the way to share configurations is by layering compose files. So when spinning up a test env I might use docker-compose...
Some nice ideas here https://medium.com/the-code-review/clean-out-your-docker-images-containers-and-volumes-with-single-commands-b8e38253c271 Make it interactive like `lucky init`. So you can choose all/unused, volumes yes/no, etc.
So that docker compose and the container processes stop
Because sometimes the modification time changes even though the file hasn't change.
When adding files to the `rebuild_when_changed` option, and then changing one of those files, I was under the impression that saving the file would auto re-build the docker container, but...
https://dev.to/kbariotis/dont-just-docker-compose-up-gff https://medium.com/the-code-review/to-boldly-log-debug-docker-apps-effectively-using-logs-options-tail-and-grep-53d2e655abcb
So if the pattern matches when running `up install` it adds the pattern to `rebuild_when_changed`
Metadata
Owner
Metadata
Up makes it easier to start, build, and run Docker for local development