Hosting and Domain
Vercel hosts and deploys the app, GoDaddy holds the domain and DNS, GitHub holds the code.
Vercel
What it does. Builds the application from GitHub on every push to main, serves it worldwide, runs the daily scheduled jobs (cron), and holds the environment variables. This docs site is a second, smaller Vercel project built from the docs-site folder of the same repository.
Where to look.
- Deployments: every build, its logs, and the one-click Promote to Production that rolls back to an earlier deploy.
- Logs: every request and the console output of each scheduled job. Filter by route, for example
/api/cron/lifecycle. - Settings, Environment Variables: the names and values the server reads. Changing one needs a redeploy to take effect.
- Settings, Cron Jobs: each job's schedule and last result.
- Settings, Domains:
www.impacthubos.comand the apex, with their DNS status.
Plan note. The Hobby plan allows daily cron jobs only, which is why the five-minute event-reminder job runs from Supabase instead.
GoDaddy
What it does. Holds the registration of impacthubos.com and its DNS records.
Records that matter.
| Record | Purpose |
|---|---|
www CNAME to Vercel | The site |
| Apex A record to Vercel | Redirects to www |
docs CNAME to Vercel | This docs site |
| Resend DKIM, SPF and return-path records | Email authentication. Without them, platform email goes to spam or bounces. |
Any _vercel TXT records | Domain verification for Vercel |
Moving the registrar means moving every record together. The email records are the ones people forget.
GitHub
What it does. Holds the source code in the repository shaun-mo/impacthub. Vercel watches the main branch. The repository is private; IHH's own account will own it after handover.
Rules. Small commits on main, rebased onto the latest, never force-pushed, so the history stays linear and a rollback is always one deploy back. Every ticket is closed with a comment saying how the feature works now.
Deploying and Rolling Back
See Deploying.