OmniDock GitHub

$ man omnidock/build-variables

OmniDock Build Variables

Configure OmniDock build-time variables for Cloudflare Git deploys, D1 binding preservation, R2 bucket binding preservation, extra R2 buckets, and Worker script naming.

Required build variables

Build variables are not runtime secrets. They are used during deploy so the Worker config can preserve bindings created in the Cloudflare dashboard.

NamePurpose
OMNIDOCK_D1_DATABASE_IDD1 database ID for the DB binding. Required to prevent D1 binding loss during updates.
OMNIDOCK_R2_BUCKET_NAMEPrimary R2 bucket name for the MAIL_BUCKET binding. Required for mail, attachments, and files.

Optional build variables

NamePurpose
OMNIDOCK_D1_DATABASE_NAMEDisplay/config convenience. The database ID is still the source of truth.
OMNIDOCK_EXTRA_R2_BUCKETSComma-separated extra buckets. Example: client-files,media-files or R2_CLIENT_FILES:client-files.
WORKER_SCRIPT_NAMEWorker script name when it differs from the default deploy name.
CLOUDFLARE_ACCOUNT_IDUseful when the API token can access multiple Cloudflare accounts.

Extra R2 buckets

Extra buckets should appear in the UI with readable bucket display names. Binding names such as R2_CLIENT_FILES are useful internally, but users should mostly see the bucket names they recognize from Cloudflare.