Moheeb Zara
295d220849
- scripts/027 (idempotent CHECK replace) + schema.sql Section 14: allow space_onboarding_steps.step_type = 'form'; referenced form id lives in the step's existing config.form_id (no new column) - finishOnboarding: a required form step is satisfied when a submission for config.form_id by the member exists (any version — re-sign is non-blocking / auto-satisfy); fails open if the form is missing or unpublished so a misconfig cannot trap a member. Probe uses the service client (submissions are forms.manage-only under RLS) - onboarding page enriches form steps with the published form def + prior-submission flag; onboarding-flow renders FormRenderer + waiver legal text/consent and submits via submitForm then marks the step done - customize: forms fetched and threaded to the onboarding panel; new "+ Form step" button + form picker writing config.form_id - validations/types/casts include 'form'; forms.test.ts +2 - docs: DATABASE_SCHEMA/DB_SCHEMA_MAP/API_REFERENCE/ARCHITECTURE/HANDOFF 287/287 tests, build exit 0. No deploy.
hackerspace-management
A multi-tenant operating system for hackerspaces, makerspaces, and member-run shops. One installation can host many independent spaces. Each space owns its own members, tasks, projects, payments, knowledge base, proposals, incidents, policies, and chat channels. All data access is enforced at the database with row-level security.
- Live site: https://hackerspace.sh
- Source: https://github.com/virgilvox/hackerspace-management
Features
- Members and tiers. Roster, tiers (Plus, Basic, Associate), roles (admin, board, treasurer, member, associate), state (current, late, inactive, unverified), per-member skills, certifications, and badges.
- Tasks and projects. Project boards, task assignment, status, area tagging, priority, comments.
- Operations. Knowledge base, secrets vault, area leads, equipment, maintenance log.
- Payments and financials. Per-member payment ledger, integration credentials per space, exports, monthly financial summary.
- Governance. Proposals with vote tracking and expiry, incident reports, policy library, area-of-interest configuration.
- Communications. Multi-channel chat with realtime delivery.
- Recruitment. Public-facing recruitment page per space.
- API. PostgREST-generated REST for every table, gated by RLS. Optional webhooks with HMAC-signed deliveries.
Stack
| Layer | Technology |
|---|---|
| App | Next.js 16, React 19, TypeScript, Tailwind v4, shadcn/ui |
| Data | PostgreSQL 17 via self-hosted Supabase |
| Auth | Supabase GoTrue, JWT, email + password |
| Realtime | Supabase Realtime (Phoenix channels over WebSocket) |
| Storage | Block volume on the host (database), local FS (uploads) |
| Resend (SMTP) | |
| Reverse proxy | Caddy 2 (automatic Let's Encrypt) |
| Tests | Vitest (unit), Playwright (end to end) |
Quick start (local development)
Requirements: Node.js 20 or later, pnpm 10 or later, Docker (for the local Supabase CLI), git.
git clone https://github.com/virgilvox/hackerspace-management.git
cd hackerspace-management
pnpm install
cp .env.example .env.local
Edit .env.local with values from your local Supabase project (see docs/LOCAL_DEV.md to start one in seconds using the Supabase CLI), then:
pnpm dev
Open http://localhost:3000, sign up, create a space, you land on the dashboard.
Detailed local setup: docs/LOCAL_DEV.md.
Production deployment
The supported production target is a single DigitalOcean Droplet running self-hosted Supabase plus the Next.js app behind Caddy with Let's Encrypt. No managed Supabase, no third-party application data store.
End-to-end guide: docs/DEPLOY_DO_SELFHOSTED.md.
Summary:
- Provision a Droplet (4 GB RAM, 2 vCPU, 80 GB disk recommended).
- Attach a block volume mounted at
/mnt/datafor the Postgres data directory and backups. - Point DNS A records for your domain,
www,supabase,studioat the Droplet. - Run the bootstrap script in
scripts/to install Docker, Supabase, Node, Caddy, the app, the systemd unit, backup cron, and the deploy hook. - Push to
main. GitHub Actions runsdeploy.shon the Droplet over SSH: pull, install, apply pending migrations, build, restart.
The deploy script is idempotent and tracked: every numbered migration in scripts/ is recorded in public._migrations_applied. New migrations are applied automatically on push.
Database
scripts/schema.sql is the canonical, idempotent, full schema. Run it once on a fresh Supabase project. Subsequent changes are added as numbered migrations (scripts/021_*.sql, 022_*.sql, etc.) and applied incrementally.
| Topic | Doc |
|---|---|
| Conventions | scripts/README.md |
| Full reference | docs/DATABASE_SCHEMA.md |
| Column map | DB_SCHEMA_MAP.md |
Documentation
| File | Contents |
|---|---|
| docs/ARCHITECTURE.md | System design, project structure, auth flow |
| docs/DATABASE_SCHEMA.md | Tables, enums, indexes, RLS policies |
| docs/API_REFERENCE.md | Server actions and REST endpoints |
| docs/COMPONENT_REFERENCE.md | UI components and props |
| docs/DEPLOY_DO_SELFHOSTED.md | End to end production deploy |
| docs/LOCAL_DEV.md | Fresh clone to running locally |
| docs/GOVERNANCE_FEATURES.md | Proposals, incidents, policies |
| docs/WEBHOOKS.md | Webhook payload, signing, verification |
| TESTING.md | Test commands and coverage |
| CONTRIBUTING.md | How to contribute |
| CHANGELOG.md | Notable changes per release |
| SECURITY.md | Vulnerability disclosure |
| LICENSE | MIT |
Scripts
pnpm dev # development server
pnpm build # production build
pnpm start # serve production build
pnpm lint # eslint
pnpm test # vitest watch mode
pnpm test:ui # vitest UI
pnpm test:e2e # playwright end-to-end
Project status
The system is feature-functional and serving production traffic at hackerspace.sh. See docs/AUDIT.md for the latest audit and the open issues list.
Contributing
Contributions are welcome. Please read CONTRIBUTING.md before opening a pull request. Security issues: see SECURITY.md.
License
MIT. See LICENSE.