━┏┓━━━━━━━┏┓━━━━━━━┏┓━┏┓━━━━━━━━━━━━━━━┏┓━
┏┛┗┓━━━━━━┃┃━━━━━━┏┛┗┓┃┃━━━━━━━━━━━━━━┏┛┗┓
┗┓┏┛┏┓┏━━┓┃┃┏┓┏━━┓┗┓┏┛┃┗━┓┏━━┓┏━━┓┏━━┓┗┓┏┛
━┃┃━┣┫┃┏━┛┃┗┛┛┃┏┓┃━┃┃━┃┏┓┃┃┏┓┃┃┏┓┃┃━━┫━┃┃━
━┃┗┓┃┃┃┗━┓┃┏┓┓┃┃━┫━┃┗┓┃┗┛┃┃┗┛┃┃┗┛┃┣━━┃━┃┗┓
━┗━┛┗┛┗━━┛┗┛┗┛┗━━┛━┗━┛┗━━┛┗━━┛┗━━┛┗━━┛━┗━┛
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
To set up this repository, run the following command in the current working directory:
docker-compose up
If you encounter issues, please use docker compose down -v
to delete all volumes and existing containers. Then try the same command above.
This allows the changes you make in your local code to be immediately reflected in the containerized app. Add the following flag to your docker run
command.
-v <path-to-directory-with-code>:/app
(replace the path with $(pwd)
for Mac/Linux or ${PWD}
for Windows if your current directory contains the code)
Should you not want to test end-to-end docker compose, you can use docker-compose-test.yml, or a different name file.. use docker compose --file docker-compose-test.yml up --build
to run this, and similarly, docker compose down
to clean it up.
docker-compose --env-file .env up --build -d
- to build with .env