Moheeb Zara
2687c1578d
A regular member granted reveal access either via the ops.secrets.read role permission or a per-secret ops_acl entry could not actually see or reveal secrets: revealSecret hard-gated on built-in role admin/board (ignoring both the permission and the ACL), and secrets_select RLS never consulted the permission, and the Ops page short-circuited the secrets fetch by built-in role. Migration 031 additively adds an OR user_has_permission(..., 'ops.secrets.read') branch to secrets_select; the admin/board and per-secret ops_acl branches are unchanged so deployment is access-neutral unless an admin has granted the permission. revealSecret now resolves the member and lets RLS be the boundary (a denied row simply does not return). The Ops page always queries secrets (RLS filters the set) and shows the section to admin/board, a permission holder, or anyone with an ACL-granted secret. Write paths (create/update/delete) are unchanged. Mirrored in schema.sql; migration docs and HANDOFF updated.
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.