San Diego DEVx Website

Welcome to the San Diego DEVx website repository! This project aims to build a vibrant community of developers in San Diego, providing a platform for networking, learning, and sharing knowledge.

Development Setup

Follow these instructions to set up the development environment and run the project locally.

Prerequisites

Make sure you have the following installed on your machine:

• Bun (latest version recommended)

Installation

1. Clone the repository:

git clone https://github.com/yourusername/san-diego-devx.git
cd san-diego-devx

2. Install dependencies:

bun install

3. Start the development server with the following command::

bun run dev

The site will be running at http://localhost:3000.

Environment Variables

Realtime doorbell interactions rely on Supabase Realtime. Create a Supabase project (free tier is fine) and add the following to .env.local:

NEXT_PUBLIC_SUPABASE_URL=<your-supabase-project-url>
NEXT_PUBLIC_SUPABASE_ANON_KEY=<your-public-anon-key>

Local Supabase Development

The repo includes a Supabase CLI project under supabase/ with config and migrations, so you can run the full stack locally.

1. Prerequisites

• Docker Desktop – Install Docker Desktop and ensure it's running before starting Supabase.
• Supabase CLI – Install the Supabase CLI for your platform.

2. Start the local Supabase stack

From the repo root:

supabase start

On success, you should see output including:

• Project URL: http://127.0.0.1:54321
• Studio: http://127.0.0.1:54323
• Database: postgresql://postgres:postgres@127.0.0.1:54322/postgres

If you change migrations or want a clean slate:

supabase stop
supabase db reset   # WARNING: destroys local data, reapplies migrations
supabase start

3. Point the Next.js app at local Supabase

Update .env.local in the project root:

NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
NEXT_PUBLIC_SUPABASE_ANON_KEY=sb_publishable_ACJWlzQHlZjBrEguHvfOxg_3BJgxAaH

Note: the sb_publishable_... key is printed in the supabase start output under “Authentication Keys → Publishable”.

Restart the dev server after changing .env.local.

4. Authentication

For local testing, username/password authentication works out of the box – just sign up with any email and password in the app.

For OAuth providers (GitHub, Google), see the Local OAuth Setup Guide.

5. Common local issues

• "no Route matched with those values" at 127.0.0.1:54321
  This is normal for the bare API root. Use Studio (http://127.0.0.1:54323) or http://localhost:3000 instead.
• Docker daemon errors (Cannot connect to the Docker daemon)
  Make sure Docker Desktop is installed and running before you call supabase start.

Contributing

We welcome contributions from the community! If you have suggestions or improvements, feel free to open an issue or submit a pull request.

Guidelines

The project uses Prettier and ESLint for code formatting and linting. Integrating ESLint in your editor is recommended to ensure that the code formatting in addition to the linting rules are followed. For VSCode, you can use the ESLint extension.

Pre-commit hooks are in place to ensure that the code is properly formatted before a commit is added to the repo. The pre-commit hook runs the precommit script (bun run precommit).

For detailed code style and organization guidelines:

• File Conventions - File structure and organization patterns for all code files
• Styling Guidelines - Styled-components usage and migration from Tailwind
• Agent Guidelines - Complete coding standards for AI agents and developers

Steps to Contribute

1. Fork the repository
2. Create a new branch:

   git checkout -b feature-name

3. Make your changes and commit

   git add .
   git commit -m "Add some feature"

4. Push to the branch

   git push origin feature-name

5. Open a pull request on Github

Footnotes

Note: This project is being refactored to use styled-components exclusively. Please do not add new Tailwind classes. See styling guidelines for details.