Production deploy completed (DigitalOcean Droplet, self-hosted Supabase, Caddy + Let's Encrypt, GitHub Actions auto-deploy on push to main, daily pg_dumpall backups). This commit lands the work that came out of the deep audit pass and the open-source release prep. Audit fixes: - Webhook signing secret is now displayed in the settings UI with show/hide and copy-to-clipboard; the broken external docs.hackerspace.sh link is replaced with a link to the new local docs. - Settings updateSpaceSettings parameter type now includes mission_statement so the field persists. - members page enforces member_directory_visibility for non-admin viewers (admin_only, board_visible, members_visible). - Mobile responsiveness pass: Projects Kanban grid, Members + Payments tables (column hiding on small screens), Proposal tally + voting buttons (2-col on mobile). Open-source release scaffolding: - LICENSE (MIT). - CONTRIBUTING.md with dev setup, conventions, PR flow. - SECURITY.md with disclosure policy. - CHANGELOG.md. - docs/WEBHOOKS.md with Node and Python signature verification examples. - README.md rewritten for an open-source audience. Removed v0/Vercel references: - @vercel/analytics dependency removed. - app/layout.tsx no longer imports Analytics, drops generator: 'v0.app'. - Canonical deployment docs (docs/DEPLOYMENT.md, docs/README.md, docs/ARCHITECTURE.md, DATABASE.md, CLAUDE.md, README.md) now describe the self-hosted Droplet target only. - e2e console-error check no longer filters [v0] noise. Landing page: - GitHub icon link to the public repo in the nav and footer.
2.6 KiB
2.6 KiB
Deployment
The supported production target is a single DigitalOcean Droplet running self-hosted Supabase plus the Next.js app behind Caddy with automatic HTTPS. The end-to-end procedure lives in DEPLOY_DO_SELFHOSTED.md.
At a glance
| Component | Hosted on |
|---|---|
| Database (Postgres) | Supabase container on the Droplet, data on a persistent block volume |
| Auth (GoTrue) | Supabase container on the Droplet |
| REST and Realtime | Supabase containers on the Droplet |
| App (Next.js) | systemd service on the Droplet, port 3000 |
| Reverse proxy | Caddy 2 on the Droplet, ports 80 and 443 |
| Resend (SMTP) | |
| Backups | Daily pg_dumpall to /mnt/data/backups, 14-day retention |
| Continuous deployment | GitHub Actions runs /opt/hackerspace-ops/deploy.sh over SSH on every push to main |
Required environment variables
All variables are listed in .env.example. At minimum:
NEXT_PUBLIC_SUPABASE_URL— public Supabase API URLNEXT_PUBLIC_SUPABASE_ANON_KEY— anon JWT, publicSUPABASE_SERVICE_ROLE_KEY— service-role JWT, server-side onlyNEXT_PUBLIC_APP_URL— public URL of the deployed app, used in OAuth redirects
How a deploy runs
- A developer pushes to
main. - GitHub Actions (
.github/workflows/deploy.yml) opens an SSH connection to the Droplet using a deploy key stored in repository secrets. - The action invokes
/opt/hackerspace-ops/deploy.sh, which:- Fetches latest
main. - Runs
pnpm install --frozen-lockfile. - Iterates over
scripts/0*.sql. Any file not present inpublic._migrations_appliedis applied and recorded. - Restarts PostgREST to refresh its schema cache.
- Runs
pnpm build. - Restarts the
hackerspace-appsystemd unit. - Probes the local app for a 200 response.
- Fetches latest
Migrations are idempotent. A redeploy that introduces no new migrations is a no-op on the database.
Local development
See LOCAL_DEV.md for the fresh-clone-to-running sequence using the Supabase CLI.
First-time provisioning
For initial server provisioning (Docker, the Supabase stack, Caddy, firewall, SSH hardening, deploy-key registration, the systemd unit, backup cron), follow DEPLOY_DO_SELFHOSTED.md end to end.
Operational checklist
- Monitor
/var/log/hackerspace-deploy.logfor deploy outcomes. - Verify backups by restoring
pg_*.sql.gzto a staging instance quarterly. - Rotate the Supabase service-role key and JWT secret if the
.envon the Droplet is ever exposed. - Keep the host OS patched. The bootstrap installs
unattended-upgrades.