Connecting local musicians, one jam at a time.
JamSesh is a web app designed to help musicians and artists connect, collaborate, and build their local music community. At its core, JamSesh functions like a forum-based social media platform—similar to Reddit—with a strong focus on location-based discovery.
Whether you're looking to join a band, find new collaborators, promote a house show, or connect with local venues, JamSesh gives users a way to plug into the "underground" music scene and make it more accessible. Inspired by apps like YikYak, posts are organized by location so users can find opportunities and fellow artists right in their town.
The goal is to foster collaboration, discovery, and connection among musicians who are often right down the street from each other but don't have a digital space to meet.
- User profiles with avatar, bio, and instrument tags
- Forum-style posts with categories (e.g., "Looking for Musicians", "Show Announcement")
- Location-based feed and map-based event discovery
- Media embedding (images, audio/video links)
- Rich text editor (TipTap) for posts
- Map pinning for events and event map view
- Modal-driven event creation and editing
- Custom SVGs for thumbnails and map pins
- Frontend: Next.js (React), TypeScript, Tailwind CSS, TipTap Rich Text Editor, React Leaflet (maps)
- Backend: Supabase (Postgres DB, Auth, Storage)
- Deployment: Vercel (recommended)
git clone <your-repo-url>
cd Jam-Sesh-webnpm install
# or
yarn installCreate a .env.local file in the root directory with the following:
NEXT_PUBLIC_SUPABASE_URL= supabase-url
NEXT_PUBLIC_SUPABASE_ANON_KEY= supabase-anon-key
npm run dev
# or
yarn devOpen http://localhost:3000 in your browser.
- Push your code to GitHub (or similar).
- Go to Vercel and import your repository.
- Set the environment variables (
NEXT_PUBLIC_SUPABASE_URL,NEXT_PUBLIC_SUPABASE_ANON_KEY) in the Vercel dashboard. - Click "Deploy".
- Build the app:
npm run build - Start the app:
npm start - Ensure environment variables are set in your hosting environment.
- Dependencies: Regularly update npm packages (
npm outdated/npm update). - Supabase: Monitor your Supabase project for usage limits and security updates.
- Environment Variables: Never commit secrets or private keys to the repo.
- Database: Use Supabase dashboard for schema changes. Back up data before making major changes.
- Testing: Test new features locally before deploying.
- Supabase connection errors:
- Double-check your
NEXT_PUBLIC_SUPABASE_URLandNEXT_PUBLIC_SUPABASE_ANON_KEYin.env.local. - Ensure your Supabase project is running and not restricted by RLS (Row Level Security) policies for development.
- Double-check your
- Build errors:
- Make sure all dependencies are installed and compatible with your Node.js version.
- Styling issues:
- If Tailwind styles are missing, try restarting the dev server and ensure
tailwind.config.tsis present.
- If Tailwind styles are missing, try restarting the dev server and ensure
- Auth issues:
- Check Supabase Auth settings (email sign-in enabled, etc.).
- Check the Next.js docs
- Check the Supabase docs
- Check the Tailwind CSS docs