ldevai/rust-crud-sql-api
ldevai/rust-crud-sql-api has 33 GitHub stars and 11 forks. GitHot measured 0 stars in 24 hours and 0 in 7 days. Last checked 2026-11-22 01:25 UTC. Last push 2026-09-28.
측정된 스타 증가
- in 24h
- 0
- in 7 days
- 0
- in 15 days
- 기록 수집 중
- in 1 month
- 기록 수집 중
서로 겹치는 기간의 순증가량이며 일별 합계가 아닙니다. 측정값이 없으면 비워 둡니다. 스타는 관심도를 나타내며 품질을 보장하지 않습니다.
소개
Rust Crud using Warp and SQL (Postgres) with JWT authentication
데이터README.md
Originalrust-crud-sql-api
A JWT-secured REST API in Rust: warp filters, Postgres through sqlx, argon2
passwords and role-based routes (User / Admin) — users, articles and comments,
laid out as routes → handlers → service per module.
Maintained in devai-io/devai_boilerplates, the public home of every devai.io project; this repo carries the same code.
Run
git clone https://github.com/ldevai/rust-crud-sql-api.git
cd rust-crud-sql-api
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 (IF NOT EXISTS), so there is no migrate step.
Without Docker: run a Postgres, export the variables from .env.example, then
cargo run (Rust 1.98, the toolchain the Dockerfile pins).
How it works
| Method | Path | Auth | Result |
|---|---|---|---|
| GET | /health |
— | 200 ok |
| POST | /api/auth/register |
— | {email, name, password} → 201 user (role User), 409 if taken |
| POST | /api/auth/login |
— | {email, password} → 200 {id, email, name, role, access_token} |
| GET | /api/articles |
— | 200 all articles, without content |
| GET | /api/articles_home |
— | 200 articles with in_home: true, without content |
| GET | /api/articles/{url} |
— | 200 full article, or 404 |
| POST | /api/articles |
Admin | {title, url, content?, tags?, in_home?} → 201, 409 if the url exists |
| PUT | /api/articles |
Admin | same body plus id → 200, or 404 |
| DELETE | /api/articles/{id} |
Admin | 204 (its comments go with it), or 404 |
| PUT | /api/articles/updateHomeView/{id} |
Admin | flips in_home → 200 article |
| GET | /api/articles/comments/{article_id} |
— | 200 comments, oldest first |
| POST | /api/articles/comments |
— | {article_id, author, email, content} → 201, 404 for an unknown article |
| DELETE | /api/articles/comments/{article_id}/{id} |
Admin | 204, or 404 |
| GET | /api/users |
Admin | 200 all users |
| GET | /api/users/{id} |
Admin | 200 user, or 404 |
| POST | /api/users |
Admin | {email, name, password, role?} → 201 |
| PUT | /api/users |
Admin | {id, email, name, role} → 200 |
| DELETE | /api/users/{id} |
Admin | 204, or 404 |
| PUT | /api/users/changePassword |
any | {id, current_password?, new_password} → 204 |
Auth — login returns an HS256 JWT signed with
AUTH_SECRET(sub= user id,role, 24 h expiry); send it asAuthorization: Bearer <token>. Verification pins HS256 and requiresexp.with_auth(env, Role::Admin)insrc/auth/middleware.rsis the warp filter that answers401without a valid token and403when the role is not enough.Passwords — argon2id (RustCrypto
argon2), hashed on tokio's blocking pool. Users change their own password withcurrent_password; admins can reset anyone's.Roles — registration always creates a
User. Promote the first admin in the database, then log in again (the role travels inside the JWT):docker compose exec db psql -U demo -d demo \ -c "UPDATE users SET role = 'Admin' WHERE email = '[email protected]'"Comments are public to read and write; the commenter's email is stored but never returned.
Errors are always JSON:
{"error": "message"}, including warp's own rejections (bad JSON400, wrong content-type415, wrong method405).
Try it:
curl -X POST localhost:8080/api/auth/register -H 'content-type: application/json' \
-d '{"email":"[email protected]","name":"Admin","password":"supersecret"}'
# promote it with the psql command above, then:
TOKEN=$(curl -s localhost:8080/api/auth/login -H 'content-type: application/json' \
-d '{"email":"[email protected]","password":"supersecret"}' | jq -r .access_token)
curl -X POST localhost:8080/api/articles -H "Authorization: Bearer $TOKEN" \
-H 'content-type: application/json' -d '{"title":"Hello","url":"hello","content":"First post"}'
curl localhost:8080/api/articles/hello
Layout
src/main.rs route tree, request log, graceful shutdown
src/environment.rs config, Postgres pool, schema bootstrap, shared filters
src/error.rs ApiError and the rejection → {"error": ...} mapping
src/auth/ JWT + argon2 (mod.rs), with_auth filter, register/login
src/users/ routes → handlers → service (sqlx queries)
src/articles/ routes → handlers → service, comments included
schema.sql tables and indexes, applied on startup
Deploy
Fork this repo (or push a copy 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. Set a long random
AUTH_SECRET on the server; the one in compose.yaml is for local use only.
Part of devai.io — Rust API boilerplates. Same API on MongoDB:
rust-crud-nosql-api; actix-web take:
rust-crud-actix-mongo-api.
관련 프로젝트 살펴보기
불러오는 중…