Support restoring databases from a local dump file (UI upload)

What problem will this feature address?

Dokploy currently allows restoring a database from backups stored in an S3 Destination.
When migrating an existing app to Dokploy, the backup/dump often already exists outside Dokploy (for example, created from a previous hosting setup). In that case, there is no direct way to restore from that local dump file through Dokploy.

This creates extra friction for migrations because users may need additional manual steps to move/import the dump first.

Describe the solution you'd like

Add support for restoring a database from a local dump file, ideally directly from the UI by uploading a file.

Possible implementation ideas:

Add a local source option in the current Restore dialog (alongside S3 Destination).
Or add a separate action/button like Restore from file / Import dump.

Expected flow:

1. User selects database.
2. User chooses “Restore from file” (or local source in restore dialog).
3. User uploads a supported dump format.
4. Dokploy runs restore/import process and shows logs/progress.

This would make migrations into Dokploy much easier.

Describe alternatives you've considered

• Uploading the dump to S3 first and restoring from S3.
• Manually restoring via CLI/container commands outside the Dokploy UI.

Both workarounds add complexity and are less user-friendly for migration scenarios.

Additional context

I’ve seen a similar concept in Coolify docs: Import backups

Open UX question:

Should this be an additional local destination in the Restore dialog or a separate Restore from dump/file button/action?

Will you send a PR to implement it?

Yes

The issue names the existing Restore dialog and S3 Destination flow but no files, tests, or entry points. Start by locating that restore flow and trace how uploads, supported dump formats, restore execution, and logs are handled. Done means a user can select a database, upload a supported local dump, run the restore, and see progress or logs in the UI.