Is your feature request related to a problem? Please describe.
Not a problem per se, but the issue is that backups include the source database name and credentials. In our workflow we sometimes need to pull down a production (or other) database into a local environment for testing and debugging.
In order to import and run the Portabase backup locally, we have to either manually edit the DB name and credentials in the backup file to match our local environment config before importing, or use the production/source DB name and credentials in our local config.
Describe the solution you'd like
A flag or setting per database that allows the backup process to generate a backup file that does not include the source database name and credentials.
Describe alternatives you've considered
N/A.
Additional context
N/A.
Is your feature request related to a problem? Please describe.
Not a problem per se, but the issue is that backups include the source database name and credentials. In our workflow we sometimes need to pull down a production (or other) database into a local environment for testing and debugging.
In order to import and run the Portabase backup locally, we have to either manually edit the DB name and credentials in the backup file to match our local environment config before importing, or use the production/source DB name and credentials in our local config.
Describe the solution you'd like
A flag or setting per database that allows the backup process to generate a backup file that does not include the source database name and credentials.
Describe alternatives you've considered
N/A.
Additional context
N/A.