Hello from RDPly (Tristate instance)

This page is served by the Worker tristate-rdply-com running in Tristate's own Cloudflare account, reached through Cloudflare for SaaS.

How to set this up

  1. Create a GitHub repo copied from the template, named <client>.rdply.com. Set the client's Cloudflare account in wrangler.jsonc and in the workflows, and make sure the Cloudflare API token used by GitHub Actions has access to that account.
  2. Push to main. The deploy workflow in GitHub Actions deploys the Worker.
  3. In the client's Cloudflare dashboard, enable Cloudflare for SaaS on their zone <client-zone> (SSL/TLS > Custom Hostnames).
  4. Run the steps workflow in GitHub Actions one step at a time, in this order. Run each step as a preview first (dry_run on), then for real: fallback-records, fallback-origin, worker-route, custom-hostname, rdply-cname, verify.
  5. Wait a few minutes for the certificate to go active. A new name can take up to 30 minutes to resolve because of DNS caching.
  6. Add Access (sign-in) in the client's Zero Trust account with the access-app step.

To undo a step, run its rollback-<step> (for example rollback-worker-route).