1
Fork 0
blog-zig-postgres/README.md
Leonardo Devai 0735e62a4c Harmonize the blog engine contract across all eight backends
published_at is now the first-publish time (null for drafts, kept across edits
and unpublish/republish), slugs collide to -2/-3 and regenerate on retitle,
every error is {"error"} with 400/401/403/404/405/409 pinned, timestamps are
RFC 3339 UTC. GUIDELINES pins the contract; each backend passes the same 59-check
end-to-end script.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01128fhuZbgivaSJvtMf4s1G
2026-09-27 21:25:37 +02:00

93 lines
4.8 KiB
Markdown

# blog-zig-postgres
A minimalist blog engine API in Zig 0.16: `std.http.Server` with a thread per
connection and an arena per request, Postgres via
[pg.zig](https://github.com/karlseguin/pg.zig), argon2id from
`std.crypto.pwhash`, and a hand-rolled HS256 JWT in about 70 lines. No web
framework.
## Run
git clone https://git.devai.io/templates/blog-zig-postgres.git
cd blog-zig-postgres
docker compose up --build
The API answers on http://localhost:8080 (`curl localhost:8080/health` → `ok`).
Postgres keeps its state in `./data/postgres`; `schema.sql` is applied on
every start (every statement is `if not exists`), so there is no migrate step.
Without Docker (Zig 0.16.0): point `DATABASE_URL` at a Postgres database,
export the variables from `.env.example`, then `zig build run`. The pg.zig
dependency is pinned by hash in `build.zig.zon` and fetched on the first build.
## How it works
| Method | Path | Auth | Result |
|--------|------------------|------|----------------------------------------------------------|
| GET | `/health` | — | `200 ok` |
| POST | `/auth/register` | — | `{email, password}` → `201 {id, email}`, `409` if taken |
| POST | `/auth/login` | — | `{email, password}` → `200 {token}`, `401` if wrong |
| GET | `/posts` | — | `200 [{id, title, slug, excerpt, published_at}]`, published only |
| GET | `/posts/{slug}` | — | `200` full published post, or `404` |
| POST | `/posts` | JWT | `{title, body}` → `201` full post (a draft) |
| PUT | `/posts/{id}` | JWT | `{title?, body?, published?}` → `200` full post |
| DELETE | `/posts/{id}` | JWT | `204` |
- **Auth** — register stores an argon2id hash (OWASP parameters, passwords of
8+ characters); login returns an HS256 JWT signed with `AUTH_SECRET`
(`sub` = user id, 7-day expiry). Send it as `Authorization: Bearer <token>`.
`src/jwt.zig` rejects any `alg` but HS256, compares signatures in constant
time and enforces `exp`.
- **Ownership** — only a post's author may update or delete it; anyone else
gets `403`.
- **Slugs** come from the title (`"Hello, World!"` → `hello-world`); a
duplicate title gets `-2`, `-3`, … Retitling a post regenerates its slug.
- **Drafts** — new posts are unpublished; `PUT {"published": true}` publishes.
Public endpoints only return published posts. `excerpt` is the first 200
characters of the body (Postgres `left()`, so never a split UTF-8
character); `published_at` is stamped the first time a post is published
(`null` until then) and kept through later edits and unpublish/republish;
the list is newest first by it. Timestamps are RFC 3339 strings in UTC.
- **Errors** are `{"error": "message"}` with a matching status code.
A full round trip:
```sh
curl -s localhost:8080/auth/register -d '{"email":"me@example.com","password":"sup3rsecret"}'
TOKEN=$(curl -s localhost:8080/auth/login -d '{"email":"me@example.com","password":"sup3rsecret"}' | jq -r .token)
ID=$(curl -s localhost:8080/posts -H "Authorization: Bearer $TOKEN" -d '{"title":"Hello, World!","body":"First post."}' | jq -r .id)
curl -s -X PUT localhost:8080/posts/$ID -H "Authorization: Bearer $TOKEN" -d '{"published":true}'
curl -s localhost:8080/posts/hello-world
```
## Layout
```
build.zig.zon package manifest and lockfile: pg.zig pinned by hash
schema.sql users + posts tables, applied on startup
src/main.zig config, listener, one thread per connection, routing
src/web.zig JSON in/out, body limit, bearer token, clock
src/auth.zig register/login, argon2id, requireAuth
src/jwt.zig HS256 sign/verify on std.crypto
src/posts.zig post handlers, slugs, ownership checks
src/db.zig queries via pg.zig, unique-slug retries
extras/ drop-in Clerk and Auth0 verifiers, each with swap steps
```
The runtime image is distroless: the binary is fully static, built with
`-Dcpu=baseline` so it runs on any CPU of its architecture. Local auth lives
in `src/auth.zig` + `src/jwt.zig`; `extras/auth-clerk/` and
`extras/auth-auth0/` each hold one JWKS-based RS256 verifier (std only) and a
README with the exact steps.
## Deploy
Push to your own GitHub repo and the shipped workflow
(`.github/workflows/ci.yml`) tests the compose stack, publishes the image to
GHCR, and — once you set the `DEPLOY_HOST` / `DEPLOY_USER` variables and
`DEPLOY_KEY` secret — deploys it to your server over ssh.
---
Part of [devai.io](https://devai.io) — the blog engine series: one API
contract, eight backends (`blog-{go,rust,zig,python}-{postgres,mongo}`) and
the `blog-react`, `blog-angular`, `blog-dart` and `blog-flutter` frontends.