Is your proposal related to a problem?
We currently found it a little confusing to discover how arbitrary dotenv files could be used.
The information is there on the Deployment page, but it was not readily discoverable from the Environment Variables page.
Describe the solution you'd like
Move the "Customizing Environment Variables for Arbitrary Build Environments" section from the Deployment page to the Environment Variables page, as a subsection to "Adding Development Environment Variables In .env".
The old section on the Deployment page will be replaced by a link pointing to the Environment Variables page.
Describe alternatives you've considered
Instead of moving the content from Deployment, we could just make a reference to it in Environment Variables.
Additional context
I'm more than happy to submit a PR for this! Wanted to create an issue first though.
Is your proposal related to a problem?
We currently found it a little confusing to discover how arbitrary
dotenvfiles could be used.The information is there on the Deployment page, but it was not readily discoverable from the Environment Variables page.
Describe the solution you'd like
Move the "Customizing Environment Variables for Arbitrary Build Environments" section from the Deployment page to the Environment Variables page, as a subsection to "Adding Development Environment Variables In .env".
The old section on the Deployment page will be replaced by a link pointing to the Environment Variables page.
Describe alternatives you've considered
Instead of moving the content from Deployment, we could just make a reference to it in Environment Variables.
Additional context
I'm more than happy to submit a PR for this! Wanted to create an issue first though.