Allow overriding environment variables per preview deployment
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?
We often work on multiple features in parallel, which means there are multiple active preview deployments at the same time.
When working on features that involve multiple applications (e.g. API + frontend), we create separate PRs and Dokploy generates preview deployments for each.
Currently, we can’t set different environment variable values for a specific preview, so we can’t point a frontend preview to its matching backend preview URL.
Describe the solution you'd like
Enable overriding environment variables per preview deployment in the UI. This would let us set custom values (like backend URLs) for each preview without affecting others.
Describe alternatives you've considered
No response
Additional context
No response
Will you send a PR to implement it?
No
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 tracing the preview deployment UI and the existing environment-variable handling. Done means a user can set custom values for one preview deployment, those values reach the preview, and other previews remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100