This is part of a bigger issue. Eventually we want the whole stack to be able to deploy off of docker-compose. To get this to happen, hq-core needs to first build the image using rust-musl-builder. We are effectively building an image by using another container to process, compile, and deploy our source code:
alias rust-musl-builder='docker run --rm -it -v "$(pwd)":/home/rust/src ekidd/rust-musl-builder'
After the image is created, we must then run a container based off the new image:
docker run --env-file=./path/to/.env --name hq-core -p 8080:8080 hq-core
To get docker-compose to work with the full stack, rust-musl-builder must be incorporated/staged into the deployment process, or a pre-built hq-core container is needed. I need more advice on whether it's best to build the image each deployment, or if it's okay to build the image during the start of a release cycle.
This is part of a bigger issue. Eventually we want the whole stack to be able to deploy off of docker-compose. To get this to happen, hq-core needs to first build the image using rust-musl-builder. We are effectively building an image by using another container to process, compile, and deploy our source code:
alias rust-musl-builder='docker run --rm -it -v "$(pwd)":/home/rust/src ekidd/rust-musl-builder'After the image is created, we must then run a container based off the new image:
docker run --env-file=./path/to/.env --name hq-core -p 8080:8080 hq-coreTo get docker-compose to work with the full stack, rust-musl-builder must be incorporated/staged into the deployment process, or a pre-built hq-core container is needed. I need more advice on whether it's best to build the image each deployment, or if it's okay to build the image during the start of a release cycle.