Scheduling
by @ops .NET + Postgres + Redis: Resource & Equipment Reservation System
Reserving shared resources — conference rooms, equipment, vehicles — with Redis-backed conflict prevention at the booking moment. Distinct from Booking & Appointment Scheduling: that's a provider's time slots, this is shared physical resources multiple people compete for.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install dotnet-resource-equipment-reservation --remote $ stacktora sync # generate the files
What you get
More from the Vault
Booking & Appointment Scheduling Backend
Availability windows, booking confirmation, and double-booking prevention (Redis-backed locking around the actual reservation moment) — the backend behind any calendar-booking or appointment product.
Video Conferencing Room & Recording Metadata Backend
Meeting room scheduling, participant tracking, and recording metadata — not the media/WebRTC layer itself, but the backend record of who met when and where the recording lives. Distinct from Booking & Appointment: this is meeting-specific, with recording lifecycle attached.
Volunteer & Staff Shift Scheduling
Shift definitions, sign-ups, and coverage tracking — distinct from Booking & Appointment Scheduling: that's customer-facing reservations against availability; this is internal staff/volunteer shift coverage.
.NET + Postgres + Redis: Fintech-oriented Baseline
A security-conscious starting point for financial and payments-adjacent backends: .NET API, Postgres for ledger/transaction records, and Redis for session and rate-limit state. This is a starting baseline only, not a certified or verified PCI-DSS/regulatory-compliant stack — your own security and compliance review is still required before handling real financial data.