inwerejosic/actix-blog-api

Purpose and entry point

Rust REST API for a blog platform. It exposes session-authenticated user, post, tag, and post–tag relationship endpoints over HTTP. Application startup, dependency initialization, middleware, and route registration are centered in src/main.rs.

HTTP/API layer

Actix-web handlers implement login/logout/current-user flows plus CRUD-oriented user, post, and tag operations. Handlers receive request data, enforce endpoint-level behavior, invoke persistence operations, and translate failures into HTTP responses.

• src/handlers.rs

• src/main.rs

• src/error.rs

Authentication and session boundary

Authentication uses bcrypt-backed password verification and cookie sessions. Session state is persisted in Redis rather than process memory, making authenticated requests depend on both the signed session cookie/secret and Redis availability. Protected operations such as /me resolve the authenticated user through this boundary.

• src/auth.rs

• src/handlers.rs

• src/main.rs

Persistence and schema lifecycle

PostgreSQL is the system of record for users, blog posts, tags, the blog_tag junction, and schema-defined comments. SQLx manages database access; startup creates or prepares the schema automatically. The database module is the persistence boundary shared by HTTP handlers.

• src/db.rs

• src/models.rs

• src/main.rs

Domain model and relationships

Typed request/response and database-facing entities represent users, posts, tags, and authentication payloads. Posts belong to users; tags attach to posts through a many-to-many junction. Post retrieval includes its tags, while attachment and detachment mutate the relation.

• src/models.rs

• src/handlers.rs

• src/db.rs

Error propagation

Application-specific errors centralize conversion of authentication, validation, database, and missing-resource failures into API responses. This keeps handlers focused on request orchestration while preserving consistent failure semantics.

• src/error.rs

• src/handlers.rs

Runtime and deployment topology

The API runs as a Rust/Actix process on port 8080, requiring DATABASE_URL, REDIS_URL, and SECRET_KEY. Docker Compose provisions API, PostgreSQL 16, and Redis 7 with persistent volumes. The Docker image is built from Dockerfile; GitHub Actions publishes it to GHCR and Docker Hub.

• Dockerfile

• docker-compose.yaml

• .github/workflows/docker-publish.yaml

• src/main.rs