Test new Retool version

💬 Account & User Management
1

Version of Retool (if self-hosted): 3.18.1

Question / Description:
Hello!

We are planning to update our self-hosted Retool app. However, before the final release, we want to check how all components will work in the new version of the application. To do this, I want to restore a database backup and additionally deploy another instance of the application.

I know that when starting the Retool application, a SELECT query is executed on a table to find the organization, its ID, etc. I am also sure that the database stores information about the license, which the self-hosted Retool instance sends to your servers.

My question is: Are there any reasons why I should not proceed with this plan? I don’t want to end up with a double billing charge or, even worse, a service block.

We just want to upgrade safely. Our current version is quite old – 3.18.1, and we want to upgrade to 3.75.25-stable. This is a big leap, and we want to test everything in parallel beforehand.

3

meme

4

Hi @Camel_Case,

Teams on the Enterprise plan can spin up as many instances as needed with their license key. Non-enterprise keys (license keys starting with `SSOP`..) are only supported for a single instance, so while we don't block you from spinning up additional test instances, having multiple instances on might impact your features and billing/user reporting.

Prior to upgrading, I highly recommend backing up the database that powers your instance, upgrading your instance incrementally (rather than jumping straight to 3.75), and scheduling downtime in advance.

Other best practices include reviewing the changes between versions and storing your ENCRYPTION_KEY environment variable, along with any environment variables specific to your instance, in a safe place.

I see in another thread that you mentioned you have already moved forward with upgrading. Did you upgrade your original instance or did you spin up a second instance?

5

Thnx! :dizzy: