Backup Database like PostgreSQL
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
When creating a self-composed database, eg. PostgreSQL, it is not possible to create a simple Backup through the backup tab.
The automated backup process is trying to run pg_dump locally inside the container or host, but PostgreSQL requires password authentication and no password has been supplied to the backup utility.
Because the backup interface lets you specify the Database Name and User, but lacks a field for the Password, pg_dump falls back to connecting without credentials and gets rejected (fe_sendauth: no password supplied).
[Sat Aug 29 16:35:09 UTC 2026] ❌ Error: Backup failed
Error: 2026/08/29 16:35:09 NOTICE: Config file "/root/.config/rclone/rclone.conf" not found - using defaults
pg_dump: error: connection to server at "localhost" (::1), port 5432 failed: fe_sendauth: no password supplied
I used obviously the following config for the composed pg database:
POSTGRES_HOST_AUTH_METHOD: "scram-sha-256"
POSTGRES_INITDB_ARGS: "--auth-host=scram-sha-256 --auth-local=scram-sha-256"
Describe the solution you'd like
Input field for the password and port.
Describe alternatives you've considered
At the moment, I am creating a volume backup But this causes the container to stop, which causes downtimes.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the backup tab and trace the automated pg_dump invocation described in the issue, including how the configured database name and user are passed through. Add password and port inputs for PostgreSQL backups, then verify that authenticated backups complete without stopping the database container or causing downtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, typescript
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100