Separation of Build and Runtime env vars for compose applications
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
I think it would let us to better organize and manage env variables used for docker builds and runtime if we have separate env vars for each.
Describe the solution you'd like
I'd like to have 2 different env vars editors in the Environment section of my compose application.
Describe alternatives you've considered
Merging all env vars into one env and separating them using specific prefix in naming.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Environment section and the existing environment-variable editor for compose applications, then trace how those variables are passed to builds and runtime. Done means the UI and compose application flow keep build variables separate from runtime variables; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, typescript
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100