Deployment from DEV to PROD via metadata DB backup and restore

💬 Self Hosted Retool
1

We are using database backups of the internal metadata DB of Retool to realize a deployment of the apps from our DEV environment into PROD environment.
If a new version is complete in DEV we backup the metadata DB and restore the backup to the metadata DB of PROD. This way all tables in metadata DB of PROD are overwritten , although there are sections in the metadata DB which we don't want to be overwritten. E.g. everything related to user accounts.
Unfortunately we don't know about the structure of the metadata DB and explicitly the users context. Therefore we cannot decide which tableswe should be omitted from backup and restore.
Is there any information available for the internal structure and contents of the metadata DB?
Does anyone use a similar proceeding for deployment? If, how do you solve the problem of user accounts?

Thanks,
Günter

2 Likes
2

Hello @gschader,

For moving apps from a DEV environment to a PROD environment, the best process is to use the export/import app via JSON functionality.

If your account is enterprise, you will also have access to version control via Github integrations as well.

We suggest not querying the app's metadata DB directly as this is not supported.

1 Like