Dokploy / Dokploy/dokploy

Improve db restore by auto populating backup info

Open
#2,849 0 comments 1 reaction 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?

The current backup screen lets us specify a specific path, db name, etc. for backups. However, when we actually go to restore, this information needs to be manually added again.

Describe the solution you'd like

It would be awesome to have a restore process pre-fill some of this info in the actual restore dialog

Image

e.g. the above could pre-fill in here for backups, selecting the latest by default, but still allowing users to interact and change as needed.

Image

This isn't a super common workflow, but would reflect some nice polish.

Since this could be specific to each backup type, a restore button on each backup card could make sense.

Lastly, it could make sense to include a DANGER dialog box for users to confirm they want to restore their backup, warning that the current database will be fully wiped. I assume most folks who actually want to perform a restore know this, but there is not much in the way of guards/warnings as to the consequences of restoring.

Describe alternatives you've considered

Just fill the info in manually

Additional context

Super low priority

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 backup screen and restore dialog, then trace how backup path, database name, and backup selection are stored and passed between them. Done means restore fields are pre-filled, the latest backup can be selected by default while remaining editable, and the consequences of restoring are clearly confirmed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
databases, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.