web

bookslot

Booking, deposits and no-show protection for appointment-based businesses.

GitHub repo (opens in a new tab) ↗

~/problem

Small appointment businesses lose revenue to no-shows and double bookings. bookslot holds a slot for a short window while the deposit is paid, releases it if payment does not arrive, and makes overlapping bookings for the same staff member impossible at the database level.

A private, multi-tenant Laravel API with a Nuxt owner and customer frontend. Customers book a slot and pay a deposit through Stripe Connect; owners manage services, availability, refunds and balance charges. Tenant isolation is enforced in Postgres itself, not only in application code.

~/highlights

  • Tenant isolation through Postgres Row-Level Security, with separate runtime (RLS-subject) and migrator roles and a dedicated tenant-isolation test suite.
  • Double-booking of a staff member prevented by a Postgres GIST exclusion constraint on a tstzrange; the test suite deliberately never runs on SQLite.
  • Stripe Connect (Express) onboarding, deposits, refunds and off-session balance charges, with signed webhook handling, event dedup and idempotent processing.
  • Hand-built RabbitMQ transport (php-amqplib) with TTL and dead-letter delayed delivery, used to release expired deposit holds and send reminders.
  • Owner routes that call Stripe use a separate auth middleware so no database transaction stays open across a network call.
  • CI runs backend and frontend checks plus gitleaks, CodeQL and dependency scanning; Playwright E2E drives the real API.

~/architecture

Architecture of bookslotNuxt frontend connects to Laravel API. Laravel API connects to PostgreSQL, Redis, RabbitMQ, Stripe. PostgreSQL has no outgoing connections. RabbitMQ connects to Laravel API. Redis has no outgoing connections. Stripe connects to Laravel API.Nuxt frontendLaravel APIPostgreSQLRabbitMQRedisStripe
Nuxt frontend → Laravel API
Public booking page and owner admin (services, availability, appointments, Stripe settings).
Laravel API → PostgreSQL, Redis, RabbitMQ, Stripe
Sanctum cookie auth, tenant-scoped controllers, Stripe-calling routes outside any open transaction.
PostgreSQL
Row-Level Security, runtime and migrator roles, GIST exclusion constraint on appointment time ranges.
RabbitMQ → Laravel API
Delayed jobs through TTL and dead-letter exchange: hold expiry, reminders, webhook processing.
Redis
Cache and sessions.
Stripe → Laravel API
Connect Express accounts, PaymentIntents, refunds, signed webhooks.

~/stack

  • Laravel 13
  • PHP 8.4
  • Nuxt 4
  • Vue 3
  • PostgreSQL
  • RabbitMQ
  • Redis
  • Stripe Connect
  • Pest
  • Playwright

~/status

Private commercial project, not deployed publicly. Built across 40 documented sessions; no real Stripe or email/SMS provider has been used (test mode and log mailer only). The README is stale; CHANGELOG and the session handoff are current.

  • bookslot-mobile Flutter customer app for booking appointments and paying a deposit.