Improve Management of Environment Variables in `docker-compose.yml`

[Sidharth-Singh10]

Description:

The current setup places all environment variables (secrets) directly in the docker-compose.yml file, which can lead to crowding and poor readability, especially for testing purposes. It would be more maintainable and secure to separate them into a dedicated file like docker_compose.toml

Proposed Solution:

• Modular Configuration: Split environment variables into a separate file (e.g., docker_compose.toml or .env) for easier management.

• Dynamic Loading: Ensure that the environment variables are loaded dynamically into the docker-compose.yml or during the container runtime.

• Use Case: This will allow cleaner separation of concerns between code, Docker configuration, and secrets, especially in a testing environment.

This would improve readability and security while reducing clutter in the docker-compose.yml.

[pr4j3sh]

A .env file would be a good choice for storing all the environment variables.

• move all the env vars to a .env file from docker-compose.yml file.
• refactor docker-compose.yml file to serve env vars via .env file.

.env file

DATABASE_URL=postgresql://db_user:db_pass@postgres:5432/rusty_db
POSTGRES_USER=db_user
# other vars

docker-compose.yml file

env_file:
      - .env

[Sidharth-Singh10]

Feel free to make a PR if you'd like to contribute. An example .env file is already provided in the repository, so you don't need to create a new one.