separate environment variables from docker-compose.yaml

Self Checks

• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

Yes, it is tedious to adjust the configuration every time.

2. Describe the feature you'd like to see

I will modify some parameters in docker-compose.yaml, but every time I upgrade, my custom parameters are overwritten. What I expect is that upgrading components does not affect my specially configured docker-compose.yaml parameters. My suggestion is to separate the environment variables from the docker-compose.yaml to the.env.

3. How will this feature improve your workflow or experience?

With this feature, if I can keep my original special configuration, I won't have to re-modify the docker-compose.yaml file every time I upgrade.

4. Additional context or comments

None

5. Can you help us with this feature?

• [X] I am interested in contributing to this feature.

That's a great idea! Separating the environment variables from the docker-compose.yaml to a .env file would definitely make it easier to maintain custom configurations. Your contribution to this feature would be highly valuable. Thank you for your interest in contributing!

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

This is a quite good one. We can take a look at this later.

Yeah, we've had this plan all along.

Close due to it's no longer active, if you have any questions, you can reopen it.