Sebastjan.

SvelteKit · TypeScript · PostgreSQL · PGroonga · pgvector · Redis · MinIO

In use. My self-hosted platform combines catalogue search and chapter reading. The React reader has been running since June 2025 while I build its SvelteKit replacement. See screenshots and explore the project.

Catalogue. The 11 October 2026 snapshot covers 242,887 titles and 2,115,308 unique chapters across 57,702 titles. These counts describe catalogue coverage and chapter availability, not locally downloaded content.

Search. PGroonga handles text search; pgvector with HNSW indexes handles embeddings. Hybrid mode combines text and semantic results. Filters cover genres, tags, authors, publishers, and chapter counts.

Storage & rendering. PostgreSQL holds metadata and MinIO holds images. The new Svelte 5 reader uses canvas rendering, a shared image cache, and controlled preloading. Sharp reads image metadata; WebSockets carry API messages.

Migration. The running reader uses React, a TypeScript/Express API, Drizzle, PostgreSQL, and Socket.IO. It stays operational until the replacement is ready.

Development. I wrote most of the reader code by hand, including the React application and its SvelteKit replacement. The reader stays private; I may release a separate manga search.

Rust · Axum · Tokio · SQLite · Redis · Alpine.js

In use. Relay is the shared entry point for my self-hosted applications, including this portfolio. Each environment has its own routing and access rules. Subroutes use longest-prefix matching at path boundaries.

Streaming. Request and response bodies stream through reqwest without buffering entire files. Inactivity limits stop stalled HTTP transfers while allowing active transfers to continue. WebSockets are forwarded separately.

Access control. Sign-in, invitations, member/admin roles, and per-environment permissions are built in. Passwords are hashed with scrypt. Redis holds sessions; SQLite stores users, configuration, and permissions.

HTTPS. rustls selects certificates through an SNI resolver. Certbot handles Cloudflare DNS challenges and renewal. The Alpine.js dashboard has no frontend build step.

Automation. I made route and access configuration available through a host-local API over a Unix socket. Coding agents use it when deploying applications in my homelab; the administrative API has no public TCP endpoint.

Rust · Axum · sysinfo · Server-Sent Events · Alpine.js

In use. Hostwatch monitors my Linux host and manages Compose projects from a browser. Its public dashboard shows selected live metrics; logs and deployment controls require administrator access.

Collection. Shared collectors read sysinfo, /proc, and /sys, including hardware sensors and UPS readings. Updates reach browsers over SSE, so each visitor does not trigger a separate collection cycle. Docker containers are grouped by Compose labels.

Live history. Host metrics update every second. The last 90 samples stay in memory, so charts appear immediately after a refresh. There is no historical metrics database.

Compose editing. Administrators can create and edit Compose files, deploy projects, and start, stop, or restart containers. YAML is validated before saving; atomic writes preserve permissions and detect conflicting edits.

Logs & permissions. Logs support ANSI colors, search, and pause. Explicit field allowlists separate public metrics from administrator-only data and controls.

Rust · Axum · SQLite · Svelte 5 · WebSockets · Docker Compose

Status. Alpha and in active development.

Files & editing. Browse, upload, download, search, and organize files, with trash and restore. The editor supports syntax highlighting and Markdown previews; conflicting changes are detected before saving.

Storage & access. Relay provides web identity. Vault keeps metadata in SQLite and files on the filesystem, with personal folders, explicit sharing permissions, administrator-managed storage allowances, and links to existing local folders.

Integrations. Optional SMB access is stable. Embeddable file pickers are still in development and experimental.