Cloudflare DNS and redirects
River Oaks Church - Updated November 2026
Cloudflare account and zone configuration is now code in riveroaks/cloudflare-infra. Use Git to change it; do not edit these resources in the Cloudflare dashboard. Dashboard edits create drift and can block the next reviewed change.
What is managed in Git
The repository uses OpenTofu (Terraform-compatible infrastructure as code), with an account root and one root for each of these five zones:
riveroaks.orgro.churchriveroaks.ccroccgoshen.orgmyriveroaks.org
It owns the adopted DNS records, redirects and other zone rules, zone settings, email routing settings and rules, River Oaks tunnels and their remote ingress configuration, and Access applications without another owner. Connector installation and credentials remain with the host owner. The ownership register records exceptions; do not import the same object into two repositories.
Request or make a change
Ask River Oaks IT with the hostname, current behavior, desired result and reason. IT can prepare the merge request (MR) if you do not edit infrastructure code.
- Check the ownership register, then edit the account or zone root on a
feat/*orbug/*branch incloudflare-infra. - Open an MR into
main. The affected root'splan: [ROOT]job runs automatically with the read-only token. Review the proposed actions and resolve drift; deletion or replacement needs a separately reviewed destructive allowlist. - Have a maintainer review and merge the MR.
- A maintainer takes a backup and runs the affected root's manual
apply: [ROOT]job onmain, then verifies the result and takes an after backup.
An MR or a merge alone does not change Cloudflare. Follow the making a change runbook; see also rollback and restore, drift and tokens.
Backups
The manual backup:export job in cloudflare-infra stores read-only exports as
maintainer-only GitLab job artifacts retained for one year. The operator also
keeps a copy off GitLab. Compare before/after exports with
ci/backup_compare.py; see the repository's
backup instructions.
Check adoption follow-ups
for export limits, including the pending Page Rules API fix. An export is
recovery evidence, not an automatic restore or proof that every app is backed up.
Application owners
Workers and application infrastructure stay with their existing repositories:
| Repository | Owns |
|---|---|
| cloudflare-short-links | Short-link Worker, D1, custom domains/routes, schedules, service tokens and admin Access apps |
| cloudflare-forms | Forms Workers, D1, attachment R2, queues, custom domains/routes, Turnstile and production time-off Access app |
| cloudflare-email | Email Workers, outbox D1, queues, domains, schedules, secrets, account budget alerts and Email Sending setup; dev also declares optional ticket-reply routing |
| cloudflare-mobile-edge | Mobile gateway Worker, bindings and custom domains |
| website | Website Workers, routes/custom domain, live-events R2, Turnstile, plus editor/publisher DNS, tunnels and Access resources until a reviewed handoff |
Cloudflare-generated DNS for Worker custom domains stays with the app owner.
Pages deployment for this staff site remains in riveroaks/docs. Check the
ownership register and the app's configuration before changing an exception;
a future transfer requires a coordinated state-only handoff.