Skip to main content

CI/CD Best Practices

Staging and Production Environments​

To make it easy to test changes to your application without affecting your production users, we recommend using separate staging and production environments. You can do this by deploying your application with different names for staging and production. For example, when deploying my-app to staging, deploy using:

dbos-cloud app deploy my-app-staging

When deploying to production, use:

dbos-cloud app deploy my-app-prod

my-app-staging and my-app-prod are completely separate and isolated DBOS applications. There's nothing special about the -staging and -prod suffixes—you can use any names you like.

info

If you manually specify the application database name by setting app_db_name in dbos_config.yaml, you must ensure each environment uses a different value of app_db_name.

Authentication​

You should use refresh tokens to programmatically authenticate your CI/CD user with DBOS Cloud.

info

Upgrading to a DBOS Cloud paid plan will unlock multi-user organizations which you can use to setup dedicated users for CI/CD.