PythonPH

Python Philippines community website — built with Django 5.2, Tailwind CSS v4, and DaisyUI.

1. Create .env (see config/environment.py for all options)

SECRET_KEY=secret
APP_ENV=development
DEBUG=true

2. Install dependencies (uses uv, Python >= 3.13)

make install-dev

3. Set up the database (SQLite in development)

make setup-db
uv run python manage.py createsuperuser

4. Set up Tailwind CSS (one-time download of the standalone CLI — no Node.js needed)

make run-tailwind-setup

5. Run the dev server with Tailwind watching for changes

make run-server-tailwind

The site will be available at http://localhost:8000.

make run            # Run Django dev server
make shell          # Django shell
make test           # Run tests
make check          # Django system checks
make collectstatic  # Collect static files
make createcachetable # Create cache table
make run-ruff       # Lint & format check (Ruff)
make run-ruff-fix   # Auto-fix lint/format issues
make run-pre-commit # Run pre-commit hooks on all files
make clean          # Remove __pycache__ and .pyc files

The source stylesheet is src/styles/main.css (Tailwind v4 + DaisyUI). The compiled output (static/css/app.css) is gitignored and built during deploy.

make run-tailwind-watch   # Watch mode during development
make run-tailwind-build   # Production build (minified)

Note: The codebase has a mix of styling approaches — the landing page uses a committed prebuilt CSS blob (Bootstrap 5 + Tailwind v2), while the jobs and auth pages use SCSS via django-compressor. The django-tailwind-cli setup is the current/modern path forward.

The jobs app exposes a REST API under /jobs/api/v1/ (Django REST Framework).

• GET /jobs/api/v1/jobs — list approved, active jobs
• GET /jobs/api/v1/companies — list companies

A GET /health endpoint returns 200 OK — useful for load balancer or monitoring probes.

./bin/build-dev    # Build the image + nginx
./bin/deploy-dev   # Start containers (web, nginx, db, source)

./bin/build        # Build the image + nginx
./bin/deploy       # Deploy (web, nginx)

Note: For the dockerized development setup, run ./bin/build-dev && ./bin/deploy-dev for changes to reflect.

Uploaded media (event cover images, volunteer/team photos) is stored in Cloudflare R2 via django-storages + boto3. Static files are unaffected and stay on WhiteNoise.

When the R2 credentials below are set, Django's default storage becomes the S3-compatible S3Boto3Storage backend pointed at your bucket. When they are missing (e.g. local development), it falls back to the local filesystem (MEDIA_ROOT / mediafiles/).

Add these to your .env (or Render env vars):

R2_ACCOUNT_ID=your-account-id
R2_ACCESS_KEY_ID=your-access-key-id
R2_SECRET_ACCESS_KEY=your-secret-access-key
R2_BUCKET_NAME=pythonph-media
R2_PUBLIC_URL=media.python.ph   # optional: custom domain

Setup steps:

1. Create an R2 bucket in the Cloudflare dashboard.
2. Create an API token with Object Read & Write permission scoped to that bucket.
3. Make the bucket publicly accessible (public bucket or a custom domain) so AWS_QUERYSTRING_AUTH=False serves files without signed URLs.
4. Set R2_PUBLIC_URL to your custom domain to serve uploaded files from it; leave it blank to use the bucket's r2.dev URL.

Deployed on Render. See render.yaml for service configuration. The build process:

1. Install dependencies with uv sync