Feature Request
Problem
Currently, when creating a MongoDB backup in Dokploy, the database name field is required. This means users must create a separate backup entry for each database in their MongoDB instance. There is no way to back up all databases at once.
Proposed Solution
Allow the database name field to be left empty for MongoDB backups. When empty, mongodump runs without the -d flag, which causes it to dump all databases in the instance.
This is a common use case — users often want a full instance backup rather than individual database backups.
Changes Required
getMongoBackupCommand — Conditionally include the -d flag only when a database name is provided
- Schema validation — Allow empty database string specifically for MongoDB (other database types still require it)
- UI — Add a hint on the database field for MongoDB: "Leave empty to back up all databases"
Additional Context
mongodump natively supports this — omitting -d dumps all databases
- This only affects MongoDB; other database types (Postgres, MySQL, MariaDB) still require a database name
- No breaking changes — existing backups with a database name continue to work as before
Feature Request
Problem
Currently, when creating a MongoDB backup in Dokploy, the database name field is required. This means users must create a separate backup entry for each database in their MongoDB instance. There is no way to back up all databases at once.
Proposed Solution
Allow the database name field to be left empty for MongoDB backups. When empty,
mongodumpruns without the-dflag, which causes it to dump all databases in the instance.This is a common use case — users often want a full instance backup rather than individual database backups.
Changes Required
getMongoBackupCommand— Conditionally include the-dflag only when a database name is providedAdditional Context
mongodumpnatively supports this — omitting-ddumps all databases