Skip to content

SELF_HOSTING_CLOUDFLARE.md

Latest commit

 

History

History
58 lines (37 loc) · 2.65 KB

SELF_HOSTING_CLOUDFLARE.md

File metadata and controls

58 lines (37 loc) · 2.65 KB
Raw

Cloudflare Self-Hosting

Host OpenSEO on Cloudflare for internet-facing self-hosting across multiple devices or with your team. It works on Cloudflare's free plan.

This doc covers initial setup with the Deploy to Cloudflare button. Related guides:

  • Manual deploy with Wrangler: use this if the deploy button fails or you want full control over resources.
  • Operations: connect the MCP server, update to the latest version, add teammates, telemetry.

1) Deploy from GitHub

Deploy to Cloudflare

Click the deploy button, there are lots of fields on the deploy form, but you only need to do the below steps.

  1. Connect your Git provider (GitHub/GitLab).
  2. Leave the resource naming fields as default unless you have a reason to change them.
  3. Click Create and Deploy.
  4. Wait 1-2 minutes for deployment to finish.

If deploy fails with Cannot provision a KV Namespace with the title "open-seo" because it already exists, use the manual deploy with Wrangler flow instead.

2) Configure authentication and secrets

In the Cloudflare dashboard:

  1. Go to Compute -> Workers & Pages -> your OpenSEO Worker.
  2. Open Settings.
  3. In Domains & Routes, enable Cloudflare Access for the workers.dev route.
  4. Save the values shown by Cloudflare Access.
  5. In Variables & Secrets, add:
    • POLICY_AUD (from Access setup)
    • TEAM_DOMAIN (domain from JWKS_URL, for example https://your-team.cloudflareaccess.com)
    • DATAFORSEO_API_KEY (see DATAFORSEO_API_KEY.md for how to get one)

3) Optional: add an R2 lifecycle rule

DataForSEO API responses are cached in R2 under the dataforseo-cache/ prefix. This step is optional, but recommended to automatically clean up expired cache objects:

npx wrangler r2 bucket lifecycle add open-seo dataforseo-cache-expiry dataforseo-cache/ --expire-days 7

If you changed the R2 bucket name during deploy, replace open-seo with your bucket name.

Without a lifecycle rule, cached objects under dataforseo-cache/ will accumulate indefinitely and increase storage costs over time.

4) Validate setup

  1. Open your Worker URL again.
  2. Sign in with Cloudflare Access.
  3. OpenSEO should load after login.

If login fails, re-check the three secrets and Access toggle.

Next steps

See Operations for connecting MCP clients, updating to the latest OpenSEO version, and giving teammates access.