About
GigLog is a diary for live music a place to record every gig and festival you've ever been to, and to find the people who were standing in the same room. You log a show (who played, where, what night), rate it, write down what you remember, and add the photos still sitting on your phone. Over time that becomes a personal history you can browse by artist, venue, city or year, with stats and achievements built from it. The social half is the point, though: because two people who separately log the same artist at the same venue on the same night resolve to the same event, the site can tell you that eleven other people were at that show, whose write-ups you can read and who you might already know. Public pages for every artist, venue, city and gig make it browsable and findable by anyone, whether or not they have an account. It currently holds 1,701 gigs from 433 people, across 2,284 artists, 542 venues and 140 cities.
How it was vibe-coded
GigLog is a Next.js 16 app (React, TypeScript, Tailwind) hosted on Vercel, with Supabase behind it providing the Postgres database, user accounts, and photo storage. Public pages artists, venues, cities, years are cached as static HTML so they load fast and are easy for search engines to index, and they refresh automatically when the underlying gigs change. Pages that need a login sit behind a separate protected section. Most data is read through database functions that return exactly the shape each page needs, which keeps permissions simple and safe. Anything that can't happen in the browser runs as a small serverless function: sending email through Mailgun, looking up artist and setlist data from MusicBrainz and Setlist.fm, and turning venue addresses into map coordinates. The database holds around 37 tables, with fuzzy text matching used to spot duplicate artist names, and a shared "event" record so several people logging the same night are recognised as having been at the same show.
