Moheeb Zara
5d153b4d68
In-app notification center (Phase 5, migration 051):
- notifications.read_at + partial unread index. /me Notifications is now
an inbox: unread styling, click to expand the message + mark read,
"mark all as read", unread count. markNotificationsRead is a service-
client write scoped to the caller's own member_id. Always-on channel:
email-muted ('skipped') notifications still appear in-app.
Consolidate /profile into /me:
- Delete app/(app)/profile/*; /me is the single member page. Port the
conflict-of-interest privileged-role nudge + last-disclosed date into
/me's profile editor. Remove the "My profile" sidebar + command-palette
entries; rename the /me nav label to "My membership". Repoint the
recruitment empty-state link to /me.
Theme realign:
- Revert the rounded-lg cards introduced in the prior /me visual pass to
rounded (the app norm, matching the former /profile). Route /me section
headers through the SectionTitle primitive.
Regression guard:
- integration/auth-embed.test.ts runs the auth layout's
space_members.select('*, spaces(*)') embed through PostgREST and fails
on PGRST201, so a future junction table cannot silently break auth again.
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), built-in roles, custom roles, state (current, late, inactive, unverified), per-member skills. A per-space permissions matrix grants capabilities to any role additively, on top of role-based RLS.
- Tasks and projects. Project boards, task assignment, status, area tagging, priority, comments.
- Operations. Markdown knowledge base and processes (with working in-document anchor links), an AES-256-GCM secrets vault revealed on demand, per-item Ops ACLs, area leads.
- Forms and waivers. An easy builder for arbitrary forms and signable waivers. Public (anonymous or signed-in) or members-only; per-submission snapshots of schema and legal text so a waiver stays valid against exactly what was signed; CSV export; optional onboarding step.
- Certifications and instructors. Certification types with optional validity periods; an Instructor capability awards and revokes them; expiry and revocation tracked; members see their own record.
- Classes. Class offerings with scheduled sessions, member signup with waitlists, attendance, and an optional certification granted on completion.
- Equipment. Tool and equipment registry with time-window reservations, no-overlap enforcement, and an optional required certification per item.
- Access control. Member access cards (the card UID is treated as a credential), a configurable per-space door integration (native HeatSync controller or generic HTTP) behind an SSRF-guarded executor, and an immutable, secret-redacted access log.
- Onboarding and invites. A configurable member onboarding flow; multi-use, expiring, role-granting invite links.
- Payments and financials. Per-member payment ledger, integration credentials per space, exports, monthly financial summary. Stripe recurring dues are a first-class integration: each space configures its own Stripe account (not Connect), members pay through hosted Checkout and self-serve cancel/update through the hosted Billing Portal (no card data on our servers), and a per-space signed webhook keeps
member_billingand member status (current/late) in sync, never auto-downgrading pastlate. - Transactional email and notifications. An idempotent notifications outbox writes dues-lifecycle emails (renewal receipt, payment failed, lapse) from the Stripe webhook; a small dispatcher cron drains them through Resend with a fair per-space queue and per-attempt idempotency. Adding other domains (bookings, forms) reuses the same outbox.
- Member self-serve portal. Every member's
/meis a tabbed portal: profile editing, dues management (Pay / Manage Billing), cancel class signups and equipment reservations, a personal payment history, and a verified self-service email change. - Governance. Proposals with quorum, vote tracking and expiry; incident reports with anonymous reporter tracking by token; versioned policy library; member forum with polymorphic comments.
- Communications. Multi-channel chat with realtime delivery.
- Recruitment. Public-facing recruitment page per space.
- API. PostgREST-generated REST for every table, gated by RLS. Webhook HMAC signing contract + secret rotation are defined; per-event delivery is a follow-up (see docs/WEBHOOKS.md).
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.