I have a proposal to better coordinate the deployment of containers. When we are developing locally, one .env configuration file may be sufficient, but when containers are used, multiple configuration files are often required to be used together.
For example, .envs/.mysql is to provide mysql deployment configure, and .envs/.redis is to provide redis configuration deployment configure。
use std::env;
fn main() {
// Read all configuration files in the following directory
// .envs
// .envs/.elasticsearch
// .envs/.redis
// .envs/mysql
// .envs/mysql/.mysql2
// .envs/mysql/.mysql1
use dotenv;
dotenv::dotenvs().ok();
for (key, value) in env::vars() {
println!("{}: {}", key, value);
}
}
In this way, I developed well with docker-compose.
I have implemented the logic, if it feels good, I will PR.
I have a proposal to better coordinate the deployment of containers. When we are developing locally, one
.env
configuration file may be sufficient, but when containers are used, multiple configuration files are often required to be used together. For example,.envs/.mysql
is to provide mysql deployment configure, and.envs/.redis
is to provide redis configuration deployment configure。In this way, I developed well with docker-compose.
I have implemented the logic, if it feels good, I will PR.