Preview deployments can't apply Environment Settings.
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?
Hi there,
I'm having trouble getting environment variables to apply correctly in preview deployments on Dokploy.
Let me explain the situation:
I have a Laravel application. When I first deployed it, there was no APP_KEY defined in the environment, which is required for the application to work properly. Without it, Laravel throws the following error:
No application encryption key has been specified.
After I created a pull request on GitHub, a preview deployment was generated automatically, but I encountered the error above.
So I went into the Preview Deployment Settings in Dokploy, added the APP_KEY environment variable, and saved it. However, the error persists, and it seems like the environment settings are not being applied to the preview deployment.
Is there a specific way to trigger these settings to take effect, or am I missing something?
Any help would be appreciated!
Thanks in advance.
Describe the solution you'd like
A way to apply the "Environment Settings" to the current running previews, individualy or globally across all the pull requests versions.
Describe alternatives you've considered
I pushed a new commit to the pull request and it works, because it rebuilds the image with the new env variables.
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 reproducing the Laravel preview deployment with an APP_KEY set in Preview Deployment Settings, then trace the settings flow for a running preview. Done means saved environment settings apply to an existing preview individually or across pull-request previews without requiring a new commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100