Skip to main content
JCR.DEV

01.1Case Plates

TrailVenture

Full-stack tour booking application, with Stripe integration.

Year
2026
Role
Solo developer
Stack
Django, Next.js, and Stripe
Lighthouse, desktop, Oct 2026
90
Performance
100
Accessibility
100
Best practices
TrailVenture home page, full length.

01 / 06Home page

screen 1 of 6: Home page

Visit live site(opens in a new tab)
Technical notes

Decisions

  1. 01Server-side moneyPrices are computed on the server and stored as integer centavos.
  2. 02Idempotent checkoutRepeat requests reuse the Stripe session; webhook replays are ignored.
  3. 03Versioned cacheOne version bump clears every catalog response; a hit costs zero queries.
Context
Booking is where pricing errors cost money. The charged price must equal the displayed price, a partial payment must resolve to a final state, and a held slot must be neither double-sold nor held indefinitely.
Role
Solo developer: architecture, backend, frontend, tests and deployment.
Approach
Django REST API behind a Next.js frontend on a single origin. The web app proxies Django paths at request time, so session and CSRF cookies stay first-party and no token is stored in localStorage. Views are thin: writes go through a service layer, reads through selectors with query-count tests. Roles are assigned server-side only.
Money
Prices are calculated server-side and stored as integer centavos. A booking holds its price for 30 minutes and checkout rejects expired holds. Stripe Checkout sessions carry an idempotency key, so a repeated request returns the existing session. The webhook verifies Stripe’s signature, records each event id before processing, and ignores replays; unexpected errors return 5xx so Stripe retries. Bookings are never deleted: unpaid holds expire on a schedule and remain on record.
Caching
Catalog responses are cached in Redis under versioned keys. Any catalog write bumps the version and invalidates every dependent response at once, with no per-key mapping to maintain. Tests assert a cache hit costs zero database queries and a miss at most four.
Correctness
108 API tests, 50 unit tests and 132 browser tests across desktop, mobile and dark mode. CI runs the browser tests against a live API, PostgreSQL, Redis and a mail server. The tests pin the core rules: signup cannot set its own role, webhook replays are no-ops, expired holds cannot be paid, and reviews require a paid, started booking. axe checks every public page in CI; Lighthouse scores 100 for accessibility and SEO.
Deployment
Two containers and PostgreSQL on Northflank, Redis on Upstash, images on Cloudinary and mail through Mailjet, on a custom domain with automatic TLS. Background tasks run in-request and hold expiry runs as a scheduled command. Holds derive from a timestamp that checkout re-checks, so enforcement never depends on the scheduler.

Full stack

  • Django
  • Django REST Framework
  • PostgreSQL
  • Redis
  • Celery
  • Stripe
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • shadcn/ui
  • TanStack Query
  • Docker
  • Playwright
  • pytest
  • GitHub Actions
Next: Steady