search

vendgine / directory

0 stars 0 forks source link

Update .env.example #65

Open piontkovsk11andre1 opened 1 year ago

piontkovsk11andre1 commented 1 year ago

The Vendgine directory should be able to start with zero configuration, but at the same time, to ensure consistency between development and production builds, it might be a good idea to define as many configurable options as possible in the .env file and use this configuration globally.

piontkovsk11andre1 commented 1 year ago

The complication here is: Some containers that uses environment variables with the database connection strings expect a specific variable name, for example POSTGRES_PASS, while others can expect POSTGRES_PASSWORD.

Other problem is that one .env file will expose a lot of out-of-context variables for some containers, that are not needed to run the app.

piontkovsk11andre1 commented 1 year ago

Additionally, it might be a good idea to make the network configurable through .env file. Subnet prefix (eg 10.0) and network name (?) could be set using the env variable to allow running multiple Vendgine instances on one host using docker-compose.