This PR makes it so that bootstrapping a local development environment for terra_algo_backtest is as close to simple as it can be with our current CI / CD pipeline, regardless of the host environment. Now all that should be needed to run the project is two simple docker compose commands.
Testing
docker-compose up prerun
docker-compose up
Intended Results
[ ] A docker image and container labelled terra_algo_backtest-prerun should be generated, as well as a .env file in the project root that contains dynamically generated environment variables for the ENV_TAG, DEPS_TAG, and BUILD_TAG keys.
[ ] A docker image and container labelled terra_algo_backtest-env with a tag matching the ENV_TAG value in the .env file should be successfully created.
[ ] A docker image and container labelled terra_algo_backtest-deps with a tag matching the DEPS_TAG value in the .env file should be successfully created.
[ ] A docker image and container labelled terra_algo_backtest-build with a tag matching the BUILD_TAG value in the .env file should be successfully created.
Notes
If you need to regenerate the .env file for whatever reason, you can do so by simply running the following command:
This PR makes it so that bootstrapping a local development environment for
terra_algo_backtest
is as close to simple as it can be with our current CI / CD pipeline, regardless of the host environment. Now all that should be needed to run the project is two simple docker compose commands.Testing
Intended Results
terra_algo_backtest-prerun
should be generated, as well as a .env file in the project root that contains dynamically generated environment variables for theENV_TAG
,DEPS_TAG
, andBUILD_TAG
keys.terra_algo_backtest-env
with a tag matching theENV_TAG
value in the .env file should be successfully created.terra_algo_backtest-deps
with a tag matching theDEPS_TAG
value in the .env file should be successfully created.terra_algo_backtest-build
with a tag matching theBUILD_TAG
value in the .env file should be successfully created.Notes
If you need to regenerate the .env file for whatever reason, you can do so by simply running the following command: