OmniDock GitHub

$ man omnidock/cloudflare

Prepare Cloudflare for OmniDock

Create the Cloudflare resources OmniDock needs: Workers, D1, R2, Email Routing, Email Sending, Worker secrets, runtime variables, and setup checks.

Required Cloudflare resources

  • A Cloudflare Worker connected to your fork.
  • One D1 database bound as DB.
  • One primary R2 bucket bound as MAIL_BUCKET.
  • Email Sending binding named EMAIL.
  • Workers Assets binding named ASSETS.
  • Email Routing configured to send selected addresses or catch-all traffic to the Worker.

First setup check

On first open, OmniDock should show a setup/check surface instead of dropping the operator directly into login. The app checks for DB, MAIL_BUCKET, EMAIL, ADMIN_PASSWORD, PRIMARY_DOMAIN, and CLOUDFLARE_API_TOKEN.

Missing items should be shown with copyable variable names and clear labels for binding, plaintext variable, or secret. That keeps the setup process repairable without exposing actual secret values in the browser.

Cloudflare API token

The API token is used for Cloudflare sync, domain checks, routing checks, and rule automation. Store it as a Worker secret and give it the least privilege needed for the zones and email operations you manage.