Cloud Config File

Run:

reflex cloud config

The command creates cloud.yml, which defines how Reflex Cloud should deploy the app.

Every field is optional:

# Basic deployment settings
name: my-app-prod                    # Optional: defaults to project folder name
description: 'Production deployment' # Optional: empty by default
projectname: my-client-project          # Optional: defaults to personal project

# Infrastructure settings
regions:                            # Optional: defaults to sjc: 1
  sjc: 1                           # San Jose (# of machines)
  lhr: 2                           # London (# of machines)
vmtype: c2m2                       # Optional: defaults to c1m1

# Custom domain and environment
hostname: myapp                    # Optional: myapp.reflex.dev
envfile: .env.production           # Optional: defaults to .env

# Google Cloud (Enterprise, requires a connected GCP account)
provider: gcp                      # Optional: defaults to reflex-cloud
gcp_connection: eu-prod            # Optional: omit to keep the app's current connection
full_deploy: true                  # Optional: omit to leave the app's hosting mode unchanged

# Additional dependencies
packages:                          # Optional: empty by default
  - procps

Organize deployments using projects:

projectname: client-alpha    # Groups related deployments

You can also specify a project uuid instead of name:

project: 12345678-1234-1234-1234-1234567890ab

Copy the project ID from the project's settings in Reflex Build.

Install additional system packages your application requires. Package names are based on the apt package manager:

packages:
  - procps=2.0.32-1  # Version pinning is optional
  - imagemagick 
  - ffmpeg      

Include local sqlite database:

include_db: true

This database is not persistent and is lost when the app restarts. Use a database service for production data.

Deployment strategy: Available strategies:

• immediate: [Default] Deploy immediately
• rolling: Deploy in a rolling manner
• bluegreen: Deploy in a blue-green manner
• canary: Deploy in a canary manner, boot as single machine verify its health and then restart the rest.

strategy: immediate

Deploy to a Google Cloud account connected to your organization instead of Reflex Cloud. Requires the Enterprise tier and a GCP account connected under Organization → Cloud Providers.

provider: gcp

An organization can connect more than one GCP account. Name which one an app deploys through:

gcp_connection: eu-prod

Run reflex cloud providers connections to list the connections available to you, with the project, region and runtime service account of each.

Leaving gcp_connection unset keeps the app on the connection it already uses. An app that has never deployed to GCP has no connection yet, so for that first deploy the unset value means your organization's default connection — which is why the options table above lists no fixed default. A connection can only be changed before the app has been deployed; afterwards, switch providers instead so the old project is torn down properly.

Two settings are ignored on this target: regions (the region comes from the connected account) and hostname. vmtype is honored — it maps onto Cloud Run CPU and memory limits.

By default a GCP-deployed app serves its frontend from Reflex's CDN. In full deploy mode the frontend is bundled into the GCP container and served on the same origin as the backend, so the whole app runs in your cloud account:

full_deploy: true

GCP only, Enterprise tier, and incompatible with a custom domain or multiple environments. Leaving full_deploy unset leaves the app's hosting mode unchanged — it is deliberately three-valued, so a config file that never mentions it does not switch an app out of full deploy. Changing the mode stops a running app so the next deploy brings it back up in the new one, and its earlier deployments stop being rollback targets: they were built for the mode it left.

Development (cloud-dev.yml):

name: myapp-dev
description: 'Development environment'
vmtype: c1m1
envfile: .env.development

Staging (cloud-staging.yml):

name: myapp-staging
description: 'Staging environment'
regions:
  sjc: 1
vmtype: c2m2
envfile: .env.staging

Production (cloud-prod.yml):

name: myapp-production
description: 'Production environment'
regions:
  sjc: 2
  lhr: 1
vmtype: c4m4
hostname: myapp
envfile: .env.production

Deploy with specific configuration files:

# Use default cloud.yml
reflex deploy

# Use specific configuration file
reflex deploy --config cloud-prod.yml
reflex deploy --config cloud-staging.yml