www.thephenom.app Runbook
The Phenom public-facing marketing and landing site, served via Cloudflare Pages from the Phenom-earth GitHub repo.
Source:
asset-registry.yaml; curl https://www.thephenom.app → HTTP 200; CF Pages Phenom-earth repo
C2PA signed · SanMarcSoft AI content credential
What it is
www.thephenom.app is the primary public website for the Phenom platform. It serves as the marketing landing page and entry point for new users. It is a static site deployed to Cloudflare Pages directly from the Phenom-earth GitHub repository. Downtime here affects brand credibility and new user acquisition.
Deployment chain
| Layer | Value |
|---|---|
| URL | https://www.thephenom.app |
| DNS | Cloudflare (proxied, orange-cloud) |
| Hosting | Cloudflare Pages |
| Repo | Phenom-earth (GitHub) |
| Branch | main |
| CI | Cloudflare Pages build on push to main |
| Build command | (configured in Cloudflare Pages project settings) |
Pushes to main on the Phenom-earth repo trigger an automatic Cloudflare Pages build and deployment. No manual deploy step is needed under normal circumstances.
Common operations
Trigger a manual redeploy
If the latest main build needs to be redeployed without a code push:
# Via Cloudflare dashboard: Pages > phenom-earth > Deployments > Retry deployment
# Or via Wrangler CLI:
npx wrangler pages deployment list --project-name phenom-earth
npx wrangler pages deployment retry <DEPLOYMENT_ID> --project-name phenom-earth
Roll back to a previous deployment
# List recent deployments
npx wrangler pages deployment list --project-name phenom-earth
# Promote a prior deployment to production
npx wrangler pages deployment tail <DEPLOYMENT_ID> --project-name phenom-earth
# Then in the Cloudflare dashboard: Deployments > [deployment] > Rollback to this deployment
Purge Cloudflare cache
# Requires CLOUDFLARE_API_TOKEN and ZONE_ID
curl -X POST "https://api.cloudflare.com/client/v4/zones/${ZONE_ID}/purge_cache" \
-H "Authorization: Bearer ${CLOUDFLARE_API_TOKEN}" \
-H "Content-Type: application/json" \
--data '{"purge_everything":true}'
Verify it is working
curl -sf https://www.thephenom.app/ | head -5
# Expected: HTTP 200, HTML content with <title> containing "Phenom"
curl -si https://www.thephenom.app/ | grep -E "^HTTP|^cf-ray|^cache-control"
# Expected: HTTP/2 200, cf-ray header present (confirms Cloudflare proxy active)
Common failure modes
| Symptom | Likely cause | Remediation |
|---|---|---|
| 502 / 504 from Cloudflare | Cloudflare Pages build failed or origin unreachable | Check Pages build log in CF dashboard; retry deployment |
| Stale content after push | Cloudflare edge cache not purged | Purge cache via API or dashboard |
| Site shows old version | Deployment queued or build failed | Check GitHub Actions + CF Pages build status |
curl returns non-200 |
DNS misconfiguration or Pages project paused | Verify DNS A/CNAME in Cloudflare; check Pages project status |
| SSL certificate error | CF certificate renewal failed | Check CF SSL/TLS settings; re-issue cert via dashboard |
Related
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.