fix: Docker Compose build

[gacanepa]

Summary

This PR improves the Docker Compose configuration by properly implementing environment variable management and enhancing security through non-root user execution.

Changes Made

• Removed hardcoded environment variables from compose.yaml
• Added proper environment variable references using ${VARIABLE} syntax
• Configured all services to run as non-root users (user: "1000:1000")
• Updated compose.env.example with all required environment variables
• Simplified the environment file configuration by removing redundant env_file directives

Motivation

• Security: Running containers as non-root users reduces potential security risks
• Configuration Management: Proper separation of configuration from code makes the application more maintainable and flexible
• Environment Flexibility: Makes it easier to switch between different environments (dev, staging, prod) by using different environment files
• Best Practices: Follows Docker and containerization best practices for configuration management

[vercel]

@gacanepa is attempting to deploy a commit to the f1-dash Team on Vercel.

A member of the Team first needs to authorize it.

[slowlydev]

thanks for the PR, any good reason why we should enable backtrace in the example?
else it lgtm :)

[gacanepa]

thanks for the PR, any good reason why we should enable backtrace in the example? else it lgtm :)

Hey, thank you for getting back to me so quickly! It is more of a personal preference based on this answer in a Rust forum. With that said, let me know if you want it removed.

[slowlydev]

thanks for the PR, any good reason why we should enable backtrace in the example? else it lgtm :)

Hey, thank you for getting back to me so quickly! It is more of a personal preference based on this answer in a Rust forum. With that said, let me know if you want it removed.

thanks for the link, it seams fine for the most part, someone mentioned anyhow and how it might affect performance when backtrace is enabled so I would not enable it in a production env but maybe in a docker compose its fine.

But lets leave it as is for now.

[slowlydev]

thanks lets ship it