cle07/vue-actix-blog

Purpose and Entry Points

A single-project content site combines a Rust/Actix Web backend with a Vue SPA. Markdown articles (from an expected articles/ source directory) are synchronized into SQLite and exposed through APIs; the frontend renders articles, timelines, and Lua-related pages.

Backend startup: src/main.rs. Frontend bootstrap: frontend/src/main.js, with HTML/Vite entry at frontend/index.html.

Backend HTTP Host

Actix Web owns production HTTP serving, API registration, and likely static SPA delivery. It is the integration boundary between browser clients, SQLite-backed article data, and Lua execution/compilation functionality.

Paths: src/main.rs, src/api.rs, src/lua.rs.

Content Synchronization and Persistence

The repository’s primary content pipeline is Markdown article files → parsed/synchronized article records → SQLite database → API responses. The checked-in frontend database artifact suggests the database may be distributed or consumed during frontend-oriented workflows, while Rust database access remains centralized.

Paths: src/db.rs, frontend/articles.db, src/api.rs.

Article API and Navigation Model

Article-oriented endpoints in src/api.rs provide the backend contract consumed by Vue views. Obsidian-style links imply article content and metadata form a graph-like navigation model rather than isolated documents; article and timeline screens are distinct consumers of this data.

Paths: src/api.rs, frontend/src/views/Article.vue, frontend/src/views/Timeline.vue.

Lua Execution Surface

Lua is a separate backend capability, exposed through an Actix endpoint rather than implemented solely in the browser. The frontend provides both a playground and dedicated Lua pages, creating a request boundary between Vue code editing/UI and Rust-side compilation or execution.

Paths: src/lua.rs, frontend/src/components/LuaPlayground.vue, frontend/src/views/Lua.vue.

Vue SPA Composition

Vue is organized around route-selected views and reusable presentation components. App.vue is the shell; router.js controls view selection; article rendering is split between wrapper and article views. Shared navigation and timeline components support cross-page movement.

Paths: frontend/src/App.vue, frontend/src/router.js, frontend/src/views/ArticleWrapper.vue, frontend/src/components/NavBar.vue.

Deployment and Runtimes

Rust/Cargo builds and runs the Actix service; Bun/Vite builds or serves the Vue application. Development uses separate servers (Vue on 5173, Actix API on 8080). Production builds frontend assets and serves the application through Actix. Docker is the deployment packaging boundary.

Paths: Cargo.toml, frontend/package.json, frontend/vite.config.js, Dockerfile.