feat(backups): Allow multiple backup destinations/schedules for the global system backup

Aperta
  • Qualcosa non va?
#5,835 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
postgresql, typescript
Ambito
backend, databases, devops

Direzione di ricerca

The payload names the Web Server > Backups page, where the global system backup accepts one S3 destination and one cron schedule, and it covers the global Postgres database and /etc/dokploy. Start from the code that stores that single destination and schedule, then decide between the two options the issue offers. Done means the system backup can target more than one destination, and the maintainers have agreed which option to build.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
What problem will this feature address?

Currently, when configuring the global system backup (Web Server -> Backups), Dokploy only allows selecting a single S3 destination and one cron schedule:

Image

(details censored for privacy)

This makes it impossible to implement a true 3-2-1 backup strategy for the Dokploy instance itself (the global postgres database and /etc/dokploy configurations).

While individual applications or project databases can have separate configs, the core server configuration is limited to just one destination, creating a single point of failure if that cloud provider goes down.

Describe the solution you'd like

I would like the ability to either:

  • Create multiple independent system backup jobs: Allowing users to click "Create Backup" multiple times on the Web Server page, assigning a different S3 destination and cron schedule to each job.
  • Select multiple destinations in a single job: Allow checking multiple pre-configured S3 providers so that the core system archive is pushed to all selected buckets sequentially or in parallel.
Describe alternatives you've considered
  • Cloud-side replication: Using AWS S3 replication to sync to Cloudflare R2, which adds overhead and cloud provider lock-in.
  • Manual crontabs on the host: Writing a custom bash script directly on the VPS to manually copy the /etc/dokploy folder and dumping the internal dokploy-postgres container using rclone. This bypasses the utility and convenience of Dokploy's UI.
Additional context

Ensuring that the master server configuration can be natively duplicated across different cloud providers or local storage (like a local MinIO instance) ensures total disaster recovery autonomy.

Will you send a PR to implement it?

No

Lingua principale
TypeScript
Stelle
38.2k
Fork
3.1k
Merge medio
2g 11m
PR unite (30g)
66

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Dokploy/dokploy

Tutte le issue di Dokploy/dokploy

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.