015 files · 151 KB
The SaaS starter
Start with accounts, organisations, email and analytics wired into a React app and Hono API.
Railway
Deploy the folder you intended, run migrations first and check the change on the live site.
5 files · 10 KB
Why I keep it
I run WithSeismic’s site, API and Postgres on Railway, with the infrastructure in TypeScript. Deploys upload a folder through the CLI, so choosing that folder is part of shipping. Merging code alone doesn’t release it.
A worktree deploy once uploaded the main checkout and reported success, but the old homepage was still live. DEPLOY.md carries the fix: name the worktree path explicitly and check for something only the new code contains. You get the infrastructure example, ignore file and API deploy script. The Railway link is my referral link.
How I use it: Ship each piece and check it live →Take the files
5 files · 10 KB
- DEPLOY.md4 KB
- README.md2 KB
- deploy.sh1 KB
- railway-config/railway.ts2 KB
- railwayignore.example474 B
Keep building your setup: The stack
Back to the shelves →025 files · 6 KB
Turborepo
Run builds, tests and type checks across your apps in dependency order, with cached results.
0316 files · 18 KB
Hono
Give your API typed routes, generated docs and a consistent error response before adding features.
048 files · 8 KB
Drizzle
Keep your database schema typed and your SQL migrations checked in beside the code that needs them.
052 files · 5 KB
Better Auth with passkeys
Keep accounts, organisations and passkey sign-in in your own Hono API and Postgres database.
069 files · 10 KB
TanStack
Keep React routes, session checks and cached server data working from the same types.
See what I ship
I’ll send you one build log a week: what I added to the library and what I shipped with it. You can unsubscribe any time.