-
Notifications
You must be signed in to change notification settings - Fork 1
Home
swayam25 edited this page Aug 26, 2026
·
5 revisions
Everything about running, developing and deploying clashwithjpa.com.
| I want to… | Page |
|---|---|
| Get the project running on my machine | Local Development |
| Know what every environment variable does | Environment Variables |
| Understand how the monorepo is laid out | Repository Structure |
| Change the database schema | Database |
| Style something, or touch any UI | Design System |
| Deploy to a production server from scratch | Production Deployment |
| Understand the reverse proxy | Traefik and Pangolin |
| See what else runs on the box | Server Services |
| Fix something that broke | Troubleshooting |
A family of FWA clans built around war-farming, running 50v50 FWA wars and CWL side by side. The repo is the site and the API behind it.
| Piece | Stack |
|---|---|
apps/web |
SvelteKit 5, Tailwind 4, prerendered and served by nginx |
apps/server |
Hono, Drizzle ORM, better-auth, OpenAPI docs rendered by Scalar |
| Data | Postgres 18, Redis 8, MinIO for uploads |
| Monorepo tooling | Turborepo, pnpm workspaces, just for every Docker and database task |
| Production | Traefik for TLS and routing, Pangolin as the ingress manager, one VPS |
Commits follow Conventional Commits:
<type>(<optional scope>): <description>
git commit -m "feat(cwl): add league filter to the roster table"
git commit -m "fix(auth): stop refresh tokens expiring early"If you touched anything visual, read Design System first. It documents the palette, spacing, radii, z-index scale and motion rules the site sticks to.
Found a vulnerability? Do not open an issue, follow SECURITY.md.