Skip to main content

Roundcube on Google Cloud Run

Roundcube is a free, open-source, browser-based IMAP webmail client. It gives users a desktop-like mail experience — folders, address book, search and message composition — against an IMAP and SMTP mail server that already exists. Roundcube is a mail client: this module deploys no mail server. It deploys Roundcube on Cloud Run v2 on top of the App_CloudRun foundation, which provisions and manages the shared Google Cloud infrastructure.

This guide focuses on the cloud services Roundcube uses and how to explore and operate them from the Google Cloud Console and the command line. For the mechanics common to every Cloud Run application — service identity, ingress and load balancing, scaling and concurrency, CI/CD, Cloud Armor, IAP, Binary Authorization, VPC Service Controls, backups, and the deployment lifecycle — refer to the App_CloudRun foundation guide rather than repeating them here.


What Roundcube costs on RAD, and how that compares​

Running Roundcube in your own GCP project costs about $70.19/month in Google Cloud charges; RAD's module fee is a one-time 75 credits (or 67.5 credits in a RAD-managed project), covering setup and support -- not the ongoing cloud bill, which Google bills you directly in your own project or RAD meters hourly in credits in a RAD-managed one. If you deploy into a RAD-managed project you can pause the whole thing for free when you are not using it -- see Pause it for free below.

What you pay on RAD​

Your own projectRAD-managed project
Module fee75 credits, once67.5 credits, once (10% lower)
BuildsIncluded in the price: no build charge to create, 5 updates a month (UTC calendar month) free and then 2 credits each, and nothing to delete or for a failed build, up to 10 failed builds a day (UTC). Lab sessions and client projects are the exception: they are still charged for build time by the minuteThe same
Google Cloud running cost~$70.19/month, billed to your own billing account at Google's list price~61 credits/day, metered hourly by RAD at list price plus margin

Your first successful deployment on RAD is free of the module fee, whatever the fee: once per account, for a module you deploy and pay for yourself (in a solution, one application's fee: the first to succeed; never a lab session or a client project).

Default running cost in your own project

ResourceUS$/month (Google list price, us-central1)
Cloud Run, 1x vCPU / 2 GiB (scaleToZero)$13.16
Cloud SQL for MySQL, 1 vCPU / 3.75 GB, zonal, 10 GB SSD$51.02
Cloud NAT and networking$5.00
Cloud Storage (add-ons, backups)$1.00
Total$70.19

How it compares​

  • Running it yourself on a bare VPS is still the cheapest cash option -- Hetzner CPX22 (2 vCPU/4GB) runs about $24/month, a DigitalOcean 2 vCPU/4GB Droplet is also $24/month, and a GCP Compute Engine e2-standard-2 (2 vCPU/8GB) is about $49/month -- plus the admin's own time for backups, security patches and upgrades, which RAD's managed Cloud SQL, Secret Manager and monitoring cover for you -- but RAD's price is never meant to beat a VPS, only to replace the admin time a VPS still needs.
  • Roundcube is a thin webmail client, not a mail server -- it is queried whenever someone checks mail, so its own compute cost is modest and the database behind it is the main standing cost.

Pause it for free: delete a RAD-managed project, restore it when you need it​

This is the headline for a RAD-managed project. Deleting a RAD-managed project first unlinks its billing, then asks Google to delete the project outright -- Google's own 30-day recoverable soft delete. Unlike deleting one module, this does not tear down Cloud SQL, any VM or the compute resource one by one: the whole project simply stops, and nothing is charged while it waits, because billing is already unlinked.

A restore is not guaranteed — keep your own backups. Google Cloud's terms do not guarantee that a restored project, or the resources in it, will be usable after it is restored, so restoring cannot be relied on as a way to recover a deleted project. Before you delete, make sure you have taken appropriate backups of the application's data and configuration and stored them outside the project. If a restore fails, or the restored project does not work, the fall-back is to redeploy the application (see the next section) and restore its configuration and data from those backups.

Restoring, within 30 days and only by the project's owner, asks Google to undelete the project and reattaches its billing account, then asks you to run Update on each deployment to confirm everything came back. Because nothing was individually destroyed, that Update finds the same resources already there -- it is a check, not a rebuild, and an Update never charges the module fee again. Updates are included in the price (5 a month for each deployment), so a restore normally costs no credits.

What this needs: you must own the project (not one RAD only manages billing for), you must restore it yourself within 30 days -- after that Google deletes it for good -- and restoring is admitted like creating a new project, so your purchased credit balance must still clear the tier's floor (100 credits for the sandbox tier most study/demo use fits). Google says most services are fully working again within 36 hours of a restore.

One real gap: nightly backups are written to a bucket inside the project, and that bucket has Cloud Storage's soft-delete explicitly turned off, so it is very likely gone as soon as you delete the project -- even though the project itself is recoverable for 30 days. If you have customised the app and want to keep that work, copy a backup out (to Google Drive, or a bucket outside the project) before deleting. For a default install with nothing irreplaceable in it, this does not matter.

Pay only while you use it, the other way: delete and redeploy​

In your own project (or once you are past the 30-day restore window above), the alternative is to delete Roundcube outright and redeploy it later. A redeploy costs the module fee again (builds are included) -- 75 credits.

Deleting saves money only once Roundcube would otherwise sit unused long enough to clear that redeploy cost against its own daily running cost -- against the own-project total above, that works out to about 3 days or more. Most of the running cost here is usually the database; it stops only when nothing else in the project uses it, so deleting this app while something else shares the project saves only this app's own compute part.

Keep data first: nightly backups go to a bucket inside the deployment and are deleted with it, so copy the latest backup out before deleting if you want to keep it.

Lab sessions and Managed Environments​

  • Lab sessions, for training: a trainer runs a session for a class. Each participant gets the app in their own Google Cloud project for 15 minutes to 24 hours, within an allowance the trainer sets. Alternatively, the trainer builds one shared environment for the whole class, and everyone uses the same application and its data. Either the trainer funds every place, or each participant pays for their own. Everything is deleted when the session ends and unused credits go back to the trainer.
  • Managed Environments, for consultancies: a partner runs the app for a client from a ring-fenced wallet it funds, and settles with the client directly. If the wallet runs low, billing pauses and the data is kept, so nobody receives an unexpected charge. At the end the partner hands the project over and the deployments become the client's own.
  • Credits can be bought in more than 20 currencies, including XAF, XOF, NGN, GHS, KES and ZAR, by card, bank transfer or mobile money.

Sources (8 October 2026): Google Cloud Billing Catalog API list prices; radmodules.dev/pricing for RAD's own fees and daily-credit estimates; https://cloud.google.com/resource-manager/docs/delete-restore-projects for the pause/restore mechanics.

1. Overview​

Roundcube runs as a PHP container (the official roundcube/roundcubemail -apache image, wrapped by a thin custom entrypoint) on Cloud Run v2. The deployment wires together a focused set of Google Cloud services:

CapabilityGoogle Cloud serviceNotes
ComputeCloud Run v2PHP/Apache service, 1 vCPU / 2 GiB by default, serverless autoscaling; scale-to-zero by default
DatabaseCloud SQL for MySQL 8.0Roundcube's own data — preferences, contacts, session data. Mail itself stays on the IMAP server
Object storageCloud StorageA generic data bucket is provisioned, but Roundcube does not read or write it
SecretsSecret ManagerAuto-generated des_key (ROUNDCUBEMAIL_DES_KEY); database password
IngressCloud Run URL / Cloud Load BalancingDefault run.app URL; optional external HTTPS load balancer + custom domain
Mail(none — external)You supply the IMAP and SMTP servers

Sensible defaults worth knowing up front:

  • No IMAP or SMTP server is configured. The module sets ROUNDCUBEMAIL_DEFAULT_HOST and ROUNDCUBEMAIL_SMTP_SERVER to empty values, and this wrapper exposes no input for them. Set them in environment_variables (Group 6) before anyone can sign in — see §3.
  • No local accounts. Users sign in with their IMAP username and password. There is no administrator account and no admin-password secret.
  • MySQL 8.0 only. The wrapper entrypoint always composes a mysql:// DSN.
  • enable_cloudsql_volume = false. The DSN uses DB_IP, the Cloud SQL private IP, so Cloud Run connects over private-IP TCP, not the Auth Proxy Unix socket.
  • Scale-to-zero is enabled by default (min_instance_count = 0, max_instance_count = 1). Cold starts add latency to the first request after idle; set min_instance_count = 1 to avoid this.
  • No separate schema job. The image runs bin/installto.sh -y on every start, which creates and upgrades the schema idempotently. Only db-init runs as a Cloud Run job.
  • Pinned image tag. application_version = "1.6.19-apache". Keep it an exact tag — a rolling tag rebuilds without producing a new revision.

2. Google Cloud Services & How to Explore Them​

All commands assume PROJECT and REGION are set. Service and resource names are reported in the deployment Outputs.

A. Cloud Run — the Roundcube service​

Roundcube runs as a Cloud Run v2 service that autoscales by request load between the minimum and maximum instance counts. Each deployment creates an immutable revision; traffic can be split across revisions for safe rollouts.

  • Console: Cloud Run → select the service for revisions, traffic, logs, and metrics.
  • CLI:
    gcloud run services list --project "$PROJECT" --region "$REGION"
    gcloud run services describe <service-name> --project "$PROJECT" --region "$REGION"
    gcloud run revisions list --service <service-name> --project "$PROJECT" --region "$REGION"

See App_CloudRun for scaling, concurrency, execution environment, and traffic splitting.

B. Cloud SQL for MySQL 8.0​

Roundcube stores its own data — user preferences, address-book contacts and session data — in a managed Cloud SQL for MySQL 8.0 instance. Mail is never stored here; it stays on the IMAP server. The service connects over the instance's private IP via TCP. On first deploy, the db-init job creates the application database and user; the schema is then created by Roundcube itself (bin/installto.sh -y) when the container starts.

  • Console: SQL → select the instance for connections, backups, flags, metrics.
  • CLI:
    gcloud sql instances list --project "$PROJECT"
    gcloud sql instances describe <instance-name> --project "$PROJECT"
    gcloud sql connect <instance-name> --user=<db-user> --database=<db-name> --project "$PROJECT"

The instance name, database, user, and password secret are in the Outputs. See App_CloudRun for the connection model, backups, and password rotation.

C. Cloud Storage​

A generic data bucket is provisioned by default (via the Foundation's storage_buckets input), but Roundcube never reads or writes it: gcs_volumes is empty, so no bucket is mounted into the container. Attachments in flight are written to container-local scratch (ROUNDCUBEMAIL_TEMP_DIR = /tmp/roundcube-temp), which is safe to lose on a cold start.

  • Console: Cloud Storage → Buckets.
  • CLI:
    gcloud storage buckets list --project "$PROJECT"

D. Secret Manager​

One application secret is generated automatically: the 24-character des_key, stored as secret-<prefix>-roundcube-des-key and injected as ROUNDCUBEMAIL_DES_KEY. Roundcube uses it to encrypt session data and the IMAP password it holds on each signed-in user's behalf. The database password is managed separately by the foundation.

  • Console: Security → Secret Manager.
  • CLI:
    gcloud secrets list --project "$PROJECT" --filter="name~des-key"
    gcloud secrets versions access latest --secret=<secret-name> --project "$PROJECT"

See App_CloudRun for injection and rotation details.

E. Networking & ingress​

The service is reachable at its run.app URL by default. An external HTTPS load balancer with a custom domain, Cloud CDN, and Cloud Armor can be layered on. Roundcube also makes outbound connections to your IMAP and SMTP servers; with the default vpc_egress_setting = PRIVATE_RANGES_ONLY, traffic to a public mail server leaves directly rather than through the VPC.

  • Console: Cloud Run (service URL); Network services → Load balancing.
  • CLI:
    gcloud run services describe <service-name> --region "$REGION" --format='value(status.url)'
    gcloud compute addresses list --project "$PROJECT"

See App_CloudRun.

F. Cloud Logging & Monitoring​

Container logs flow to Cloud Logging; Cloud Run and Cloud SQL metrics flow to Cloud Monitoring. The uptime check is off by default (uptime_check_config.enabled = false); alert policies are optional.

  • Console: Logging → Logs Explorer; Monitoring → Dashboards / Alerting.
  • CLI:
    gcloud run services logs read <service-name> --project "$PROJECT" --region "$REGION" --limit 50

3. Roundcube Application Behaviour​

  • Pointing Roundcube at a mail server. Roundcube_Common sets these environment variables, and environment_variables (Group 6) is merged over them, so that is where you configure the mail server:

    VariableDefaultMeaning
    ROUNDCUBEMAIL_DEFAULT_HOST""IMAP server users sign in against. ssl://host for implicit TLS, tls://host for STARTTLS; a bare host name is cleartext.
    ROUNDCUBEMAIL_DEFAULT_PORT993IMAP port — 993 for implicit TLS, 143 for STARTTLS.
    ROUNDCUBEMAIL_SMTP_SERVER""SMTP server used for sending.
    ROUNDCUBEMAIL_SMTP_PORT587Submission port — 587 or 465. Never 25: Google Cloud blocks outbound port 25.
    ROUNDCUBEMAIL_SKINelasticRoundcube skin.

    Roundcube_Common has imap_host/imap_port/smtp_host/smtp_port/skin inputs that feed these values, but Roundcube_CloudRun does not declare or forward them, so on this wrapper environment_variables is the only way in.

  • Sign-in. Open the service URL and sign in with an account on the IMAP server. Roundcube has no local or administrator accounts.

  • Database DSN. The wrapper entrypoint composes ROUNDCUBEMAIL_DSNW=mysql://DB_USER:<password>@DB_IP:DB_PORT/DB_NAME with the password URL-encoded by PHP's rawurlencode, sets ROUNDCUBEMAIL_DSNR to the same value, and hands off to the image's own /docker-entrypoint.sh. The vendor entrypoint would otherwise interpolate the password raw, which fails on the @ : / ? # % & + characters Cloud SQL passwords contain.

  • Schema. There is no schema job: the image runs bin/installto.sh -y on every start, creating the schema on first boot and upgrading it after a version change.

  • PHP memory limit. php_memory_limit reaches the container as PHP_MEMORY_LIMIT; the entrypoint writes it into /usr/local/etc/php/conf.d/zz-rad-overrides.ini, overriding the image's own memory_limit=64M. The container log confirms it at start: [startup] PHP memory_limit set to 512M via ....

  • Health check behaviour. Both probes are HTTP GET /, where Roundcube serves its login form. The startup probe allows a 30 s delay plus 20 × 15 s attempts, because the image runs installto.sh and waits for the database before Apache starts.

    curl -s -o /dev/null -w "%{http_code}\n" "$SERVICE_URL/"   # expect 200
  • Inspect job execution:

    gcloud run jobs list --project "$PROJECT" --region "$REGION"
    gcloud run jobs executions list --job <job-name> --project "$PROJECT" --region "$REGION"

4. Configuration Variables​

Variables are grouped exactly as they appear on the deployment platform. Only settings specific to or notable for Roundcube are listed; every other input is inherited from App_CloudRun with its standard behaviour.

Group 1 — Project & Identity​

VariableDefaultDescription
project_id(required)Target Google Cloud project.
tenant_iddemoShort suffix (1–7 lowercase alphanumeric characters) that makes resource names unique per environment.
regionus-central1Region for the service and regional resources.

Group 2 — Deployment Environment​

VariableDefaultDescription
support_users[]Emails granted project access and monitoring alerts.
resource_labels{}Labels applied to all resources.

Group 3 — Application Identity​

VariableDefaultDescription
application_nameroundcubeBase name for resources. Do not change after first deploy.
display_nameRoundcubeHuman-readable name shown in the Console.
application_version1.6.19-apacheroundcube/roundcubemail tag, passed as the ROUNDCUBE_VERSION build ARG. This wrapper's value is the one that wins. Pin an exact -apache tag.
php_memory_limit512MPHP memory_limit, applied through conf.d/zz-rad-overrides.ini.
admin_emailadmin@example.comNo effect — Roundcube creates no accounts.
enable_gcs_storage_volumetrueNo effect — Roundcube_Common declares it but never uses it; nothing is mounted.

Group 4 — Runtime & Scaling​

VariableDefaultDescription
deploy_applicationtrueSet false to provision infrastructure only.
container_image_sourcecustomBuilds the wrapper image via Cloud Build. "prebuilt" skips the wrapper entrypoint, so the DSN is no longer URL-encoded and php_memory_limit stops working.
cpu_limit1000mCPU per instance.
memory_limit2GiMemory per instance.
min_instance_count00 enables scale-to-zero.
max_instance_count1Autoscaling upper bound.
container_port80Apache listens on port 80.
execution_environmentgen2Gen2 required for GCS Fuse mounts.
timeout_seconds300Max request duration.
enable_cloudsql_volumefalseThe DSN uses DB_IP over TCP; the socket is not used.
enable_image_mirroringtrueMirror the image into Artifact Registry.
container_protocolhttp1HTTP/1.1.

Group 5 — Access & Ingress Control​

VariableDefaultDescription
ingress_settingsallPublic ingress by default.
vpc_egress_settingPRIVATE_RANGES_ONLYRoute only RFC 1918 traffic via VPC. Use ALL_TRAFFIC only if the IMAP/SMTP servers must be reached through the VPC.
enable_iapfalseRequire Google sign-in in front of the Roundcube login.
iap_authorized_users / iap_authorized_groups[]Who may access through IAP.

Group 6 — Environment Variables & Secrets​

VariableDefaultDescription
environment_variables{}Extra non-secret settings, merged over the module defaults. Set ROUNDCUBEMAIL_DEFAULT_HOST, ROUNDCUBEMAIL_DEFAULT_PORT, ROUNDCUBEMAIL_SMTP_SERVER, ROUNDCUBEMAIL_SMTP_PORT and, optionally, ROUNDCUBEMAIL_SKIN here.
secret_environment_variables{}Map of env var → Secret Manager secret name.
protect_sensitive_environment_variablestrueCredential-named keys typed into environment_variables are moved into Secret Manager automatically.
secret_propagation_delay30Seconds to wait after secret creation before proceeding.
secret_rotation_period2592000sSecret Manager rotation notification frequency.

Group 7 — Backup & Restore​

VariableDefaultDescription
backup_schedule0 2 * * *Automated backup cron (UTC).
backup_retention_days7Retention; raise for production.
enable_backup_import / backup_source / backup_uri / backup_formatrestore optionsRestore from a backup on deploy.

Group 8 — CI/CD & Binary Authorization​

Standard App_CloudRun Cloud Build / Cloud Deploy integration — see App_CloudRun. Key inputs: enable_cicd_trigger, github_repository_url, github_token, enable_cloud_deploy, enable_binary_authorization.

Group 9 — Custom SQL Scripts & NFS server​

enable_custom_sql_scripts, custom_sql_scripts_bucket, custom_sql_scripts_path, custom_sql_scripts_use_root — run SQL from a GCS bucket after provisioning. nfs_instance_name / nfs_instance_base_name select or name an NFS VM, and only matter if enable_nfs is turned on. See App_CloudRun.

Group 10 — Load Balancer, CDN & Image Retention​

VariableDefaultDescription
enable_cloud_armorfalseProvision Global HTTPS LB + Cloud Armor WAF.
admin_ip_ranges[]CIDR allowlist for privileged access.
application_domains[]Custom domain names for the HTTPS LB.
enable_cdnfalseEnable Cloud CDN on the HTTPS LB backend.
max_images_to_retain / delete_untagged_images / image_retention_days7 / true / 30Artifact Registry cleanup policy.

Group 11 — Storage & Filesystem​

VariableDefaultDescription
create_cloud_storagetrueCreate the generic data GCS bucket. Not read or written by Roundcube.
enable_nfsfalseNot needed — the image declares no volumes and keeps no state on disk that must survive a restart.
nfs_mount_path/var/lib/roundcubeMount path, only used when enable_nfs = true.
gcs_volumes[]GCS Fuse volume mounts (requires gen2). Empty — nothing is mounted.
manage_storage_kms_iam / enable_artifact_registry_cmekfalseCMEK options.

Group 12 — Database Backend​

VariableDefaultDescription
database_typeMYSQL_8_0Must stay MySQL — the entrypoint composes a mysql:// DSN. The picker also offers POSTGRES and NONE; neither works.
db_name / db_userroundcubeTenant-prefixed at deploy time. Immutable after first deploy.
database_password_length32Generated password length (16–64). Set once — changing it on a running deployment breaks database authentication.
enable_auto_password_rotationfalseAutomated database password rotation.
rotation_propagation_delay_sec90Wait after rotation before restarting the service.
db_host_env_var_nameDB_IPAdditional name for the DB host IP. The Foundation already injects DB_IP, which is what the entrypoint reads, so the default only duplicates it.

Group 13 — Jobs & Scheduled Tasks​

VariableDefaultDescription
initialization_jobs[]Leave empty to use the built-in db-init job. Supplying any list replaces it.
cron_jobs[]No platform-scheduled recurring tasks by default.

Group 14 — Observability & Health​

VariableDefaultDescription
startup_probeHTTP GET /, 30s delay, 10s timeout, 15s period, 20 retriesWaits for installto.sh and the database before Apache starts.
liveness_probeHTTP GET /, 60s delay, 10s timeout, 30s period, 3 retriesThe login form at the document root.
uptime_check_config{ enabled = false, path = "/" }Cloud Monitoring uptime check — off by default.
alert_policies[]Metric alert policies.

Group 21 — Redis​

VariableDefaultDescription
enable_redisfalseThis module wires no Redis integration into Roundcube.
redis_host""Redis endpoint.
redis_port6379Redis port.

Group 22 — VPC Service Controls & Audit Logging​

VariableDefaultDescription
enable_vpc_scfalseEnforce a VPC-SC perimeter (requires organization_id).
enable_audit_loggingfalseDetailed Cloud Audit Logs.

5. Outputs​

Returned on a successful deployment — the quickest way to locate and explore the running resources.

OutputDescription
service_nameCloud Run service name.
service_urlDefault run.app URL of the service.
service_locationRegion the service runs in.
stage_servicesCloud Deploy stage services (when enabled).
load_balancer_ip / load_balancer_urlExternal HTTPS load balancer IP / URL (when enabled).
database_instance_nameCloud SQL instance name.
database_name / database_userApplication database name / user.
database_password_secretSecret Manager secret holding the DB password.
database_host / database_portDB endpoint / port.
storage_bucketsCreated Cloud Storage buckets.
network_name / network_exists / regionsVPC network, presence, regions.
container_image / container_registryDeployed image and Artifact Registry repo.
monitoring_enabled / monitoring_notification_channels / uptime_check_namesMonitoring status, channels, uptime checks.
initialization_jobsNames of the setup jobs (db-init).
deployment_id / tenant_id / resource_prefixNaming identifiers.
project_id / project_numberProject identifiers.
cicd_enabled / github_repository_url / github_repository_owner / github_repository_name / cicd_configurationCI/CD status and details.
artifact_registry_repository / cloudbuild_trigger_name / cloudbuild_trigger_idRegistry and build trigger.
vpc_sc_enabled / vpc_sc_perimeter_name / vpc_sc_dry_run_modeVPC-SC status.
audit_logging_enabled / artifact_registry_cmek_enabledAudit logging and CMEK status.

6. Configuration Pitfalls & Sensible Defaults​

Risk: Critical (data loss / outage / security) — High (service degraded) — Medium (cost or partial degradation) — Low (minor).

Inherited plan-time validation. This module passes its configuration through the App_CloudRun foundation engine, which validates values and combinations at plan time. Invalid configuration fails the plan with a clear, named error before any resource is created, so most mistakes below are caught up front rather than at apply or runtime.

SettingSensible valueRiskConsequence if wrong
ROUNDCUBEMAIL_DEFAULT_HOST / ROUNDCUBEMAIL_SMTP_SERVER (via environment_variables)Your IMAP and SMTP serversHighLeft empty by default. The service is healthy and serves its login form, but no user can sign in or send mail. A green health check is not evidence that mail works.
ROUNDCUBEMAIL_SMTP_PORT587 or 465HighGoogle Cloud blocks outbound port 25 for all egress; sending through port 25 never succeeds.
ROUNDCUBEMAIL_DEFAULT_HOST schemessl://host or tls://hostHighA bare host name connects in cleartext, sending users' IMAP passwords unencrypted. Use a bare host only for a server inside the VPC.
ROUNDCUBEMAIL_DES_KEY (auto-generated)Never hand-edit in Secret ManagerHighIt encrypts session data and the stored IMAP passwords. Changing it signs every user out; removing it makes the vendor image mint a different key per container, logging users out at random across instances and cold starts with nothing in the logs.
container_image_sourcecustomCriticalprebuilt deploys an image without the wrapper entrypoint — the database password is no longer URL-encoded into the DSN, so the connection fails on the punctuation Cloud SQL passwords contain.
database_typeMYSQL_8_0CriticalThe entrypoint always builds a mysql:// DSN. Any other engine (or NONE) leaves Roundcube without a usable database.
application_versionAn exact -apache tagMediumlatest or a rolling 1.6.x-apache tag can change content under the same tag string, which produces no Terraform diff and no new revision — the running container silently keeps the old image. The -fpm variants have no web server.
db_name / db_userSet onceCriticalImmutable after first deploy; renaming recreates the DB/user and loses stored preferences and contacts.
database_password_lengthSet once, at first deployHighChanging it on a running deployment writes a new password the database does not hold, and every connection fails until the database job is re-run.
php_memory_limit512M or higherMediumThe image's own default is 64M; large messages and attachments are where a small PHP heap runs out.
admin_email, enable_gcs_storage_volumeLeave as-isLowNeither has any effect on this module, whatever their descriptions say.
min_instance_count1 for productionMediumScale-to-zero (0) adds cold-start latency, including the installto.sh run, to the first request after idle.
enable_cloud_armorenable for productionMediumThe login form is publicly reachable without WAF protection by default.

For the foundation behaviour referenced throughout — service identity, scaling and concurrency, ingress and load balancing, CI/CD, Cloud Armor, IAP, Binary Authorization, VPC-SC, backups, and image mirroring — see App_CloudRun. Roundcube-specific application configuration is described in Roundcube_Common.

Need RAD to do something it does not do yet? Request it on the roadmap, or vote on what is already there.