Dokploy / Dokploy/dokploy

feat: Add global 'Run All Active Backups' button

Open
#5,087 1 comment 0 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?

Currently, Dokploy requires users to navigate to each individual application, database, or volume to trigger a manual backup. For servers running multiple active services, verifying or forcing an immediate backup before server maintenance, kernel updates, or migrations is tedious and error-prone.

Describe the solution you'd like

I would like a global "Run All Active Backups" button in the main Backups panel or the cluster Dashboard. Clicking this button would automatically queue and trigger all active database and volume backup schedules simultaneously (or sequentially) without overriding their individual automated cron patterns.

Describe alternatives you've considered

Manual click-throughs: Manually going through dozens of services to click "Backup Now" one by one, which takes time and opens up room for human error.

Additional context

This feature would bring Dokploy closer in line with robust cluster management tools, making it significantly safer for users to perform quick backups right before executing server reboots or major Dokploy version upgrades.

Will you send a PR to implement it?

No

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 or tests are named. Start by locating the main Backups panel or cluster Dashboard and tracing the existing individual “Backup Now” flows for database and volume services. Done means a global control can trigger all active backup schedules without changing their automated cron patterns.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
databases, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.