Dokploy / Dokploy/dokploy

Graceful server reboot

Open
#1,896 0 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Sometimes, it's required to reboot a server (or the server, I only use one). When doing so, however, I sometimes noticed that my databases do not handle this well (in particular, I had to use pg_resetwal a few times and got inconsistencies that I haven't yet been able to recover from in one case).

Therefore, the obvious solution is to shutdown all databases (and everything else too, really) before rebooting the server. However, to do this, one has to go through each project individually.

Describe the solution you'd like

It would be amazing if there was a "Shut down all projects" option somewhere, and one to restart them after rebooting.

Additionally, it would be amazing if this functionality (stopping everything, and starting everything that was not already stopped anyways before) was available through the API too – this would safe me from many lines in my backup script. But for me it'd already be great if the UI was there.

Describe alternatives you've considered

Another option would be a "restart server" button in the UI, however, that'd potentially be less flexible; I could imagine there being other usecases for the "shut down everything" option than rebooting the service.

Additional context

No response

Will you send a PR to implement it?

Maybe, need help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating how projects are shut down and started, then identify the existing UI and API controls involved. Done should include a way to stop all projects, restart only those that were running, and expose equivalent API functionality.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.