Restart Dokploy after
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 have a daily cron to update Dokploy as described in the docs:
curl -sSL https://dokploy.com/install.sh | sh -s update
When I open the dashboard, the new Dokploy version is not visible.
I need to restart the service via:
docker service update --force dokploy
But this is done even if there is no new Dokploy version.
Describe the solution you'd like
I would like to have some option like --restart-on-new-version:
curl -sSL https://dokploy.com/install.sh | sh -s update --restart-on-new-version`
Describe alternatives you've considered
Improve the cron script to manually check if the version is updated and restart only in that case.
Additional context
No response
Will you send a PR to implement it?
Yes
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 reading the update path in install.sh and the command entry point used by sh -s update. Run the documented curl update command to understand its current behavior. Done means the new option restarts the Dokploy service only when a new version was installed, while leaving updates without a new version untouched.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100