Text version of the portfolio of Rémi Moreau, a BTS SIO SISR student (French two-year degree in IT infrastructure and networks). Open in RémiOS, the interactive version → · Version française

Hermes Dashboard (dashu) — a self-hosted workspace

Type
Personal project
Date
November 2026
Status
v1 in service, v2 in progress
Technologies
Rust, htmx, SQLite, ffmpeg, Proxmox, LXC, Debian, systemd, Cloudflare, Tailscale, OpenID Connect, GitHub Actions, Lighthouse, Claude Code
Skills
B1.1 Manage IT assets; B1.4 Work in project mode; B1.5 Make an IT service available to users; B1.6 Organise one’s professional development

Context

Between my BTS (timetable on Pronote Campus), my work-study job at 1Life and my personal life, my notes, tasks and calendars were scattered across several apps. I wanted one place of my own, hosted at home: a kind of personal Microsoft 365, built to measure rather than an off-the-shelf dashboard.

I also turned it into a project-management exercise: write a real specification with testable acceptance criteria, have it built by an AI (Claude), and keep control of the choices, the deployment and the validation.

Since 12 November 2026, the app is displayed as Hermes Dashboard, like my other projects; dashu remains its code name (repository, program, commands).

Objectives

Implementation

The specification. I wrote the specification: scope of version 1 and what it leaves out, technologies, data model, performance and security requirements, deployment, and 14 acceptance criteria. A tracking file states, for each criterion, whether it is verified, where and how, and lists the deviations from the specification with their reasons. Every later change (files, spaces and tools, command bar, folders) got its own section, with its own criteria, written before the code.

The application. A single program written in Rust, which builds the pages on the server; the htmx library keeps navigation smooth, without reloading the page. The data lives in an SQLite database, with full-text search. Notes are edited already formatted, as in Notion (a "/" menu inserts headings, lists, tables or images), but are still saved as Markdown. The timetable is synced every hour from the Pronote Campus iCal link. A command bar, opened with "/", makes everything doable from the keyboard. A JSON API, protected by a token, lets Hermès, my AI agent, manage my tasks and notes, and read my calendar.

Security.

Version 2: files and folders.

Deployment on my homelab.

Operations.

Project tracking. After version 1, every change went through a pull request, tested before being merged: the API for Hermès, an overview of all calendars in the Personal space, navigation without a black flash, a "Dynamic Island" style space switcher with swipe-to-switch, a shortcut bar on phones, installation as an app on the iPhone home screen. Then custom spaces (up to eight), a modular dashboard, version 2 with files, the command bar that replaces the Ctrl+K palette, the new note editor and folders.

Built with Claude Code. My role: define the need, make the choices and test. I did the deployment and operations myself on my server (Proxmox, Cloudflare, Tailscale, Google, backup and restore), guided step by step.

Diagram of the dashu architecture: my computer and my iPhone reach dashu through the Cloudflare tunnel (app.dashu.dev, no open port) or through the Tailscale VPN. Hermès, my AI agent, goes through Tailscale for the JSON API and for SSH limited to six actions. On the Proxmox server, a Debian LXC container runs cloudflared and tailscale serve, which forward to dashu (Rust binary, systemd service), its SQLite database backed up every night, and the operations scripts.
Architecture: two ways in without an open port, one LXC container on my homelab

Source code: github.com/moreauremi/dashu · Project page: dashu.dev

Screenshots

Screenshots of version 1, from 11 November 2026, taken on a copy of dashu filled with demo data (fake classes, fake notes). The last one is the real output of the restore on my server. Since then, the editor shows a single formatted view, and the Ctrl+K palette has become the command bar.

Dashboard of the School space in dark theme: upcoming classes with times and rooms, today's tasks with one ticked, recent notes and a clock. At the top, the island with the three spaces, School selected.
Dashboard of the School space: upcoming classes, today's tasks, recent notes
Calendar of the Personal space in light theme, week of 16 November: the School classes on Monday and Tuesday, the Work schedule from Wednesday to Friday, and personal appointments. Each event shows the name of its space.
Personal calendar: an overview of every space
Editor of the note "VLAN et trunk 802.1Q": Markdown on the left, the preview on the right with headings, a list, a block of Cisco commands and a table of VLANs, and the tags #bts and #réseau.
Markdown editor, with live preview and autosave
Command palette opened with Ctrl+K: searching for "vlan" finds the note "VLAN et trunk 802.1Q" in the School space, with the search word highlighted.
Ctrl+K palette: search every note from the keyboard
Three iPhone screens in dark theme: the dashboard of the School space, the Personal calendar scrolling horizontally, and the list of notes with their tags. At the bottom, the shortcut bar: Dashboard, Notes, Agenda, Search.
On iPhone, as an app on the home screen: island at the top, shortcuts at the bottom
Server terminal: dashu-restore lists the backups from newest to oldest, then restores dashu-2026-11-11_183222.db. The current database is first backed up and checked, then the restore finishes and shows the command to roll back.
Restore drill on the server, 11 November 2026

Results and testing

Difficulties encountered

The site unreachable on my home Wi-Fi. app.dashu.dev worked on 4G but not at home. The router's DNS was still holding an old answer, "this name does not exist", from before the domain moved to Cloudflare. I saw it by comparing the answers of the router's DNS and of Cloudflare's (1.1.1.1). On a Mac, nslookup queries the DNS server directly, whereas the browser goes through the system cache: dscacheutil showed me what the browser actually saw. Solution: my devices use the DNS servers set by Tailscale instead of the router's.

An update that could be wrong. Reviewing the update script revealed a flaw: if compilation failed, the source code was already up to date but the running program was not, and the next update replied "already up to date" without recompiling. Fix: the version actually in service is recorded separately, and the status command reports any mismatch.

A backup that has never been restored proves nothing. The backup ran every night, but nothing showed it could be put back. I did the drill on the server without losing anything: the current database is set aside before each restore, and a test note proves that the data really comes from the backup.

Zoom on iPhone. Added to the home screen, the app could be zoomed like a web page, and iOS has ignored the standard setting since iOS 10. Solution: a web app manifest, and pinch blocking only in app mode. In Safari, zoom is still possible, for accessibility.

Compression that worked everywhere except on the server. The "Compress" button failed in production while every test passed. Two causes, specific to the service's systemd sandbox, which is absent locally and in the tests: RestrictSUIDSGID=yes refuses any chmod that sets the setgid bit, and each folder listed in ReadWritePaths is a separate mount point, so a plain rename from one folder to the other fails (EXDEV). Fix: no more setgid bit, and a copy followed by a delete when the rename fails. So that the bug does not come back, the CI now replays this sandbox.

A skewed measurement. The first Lighthouse run on the dashboard scored about 94, below the target: my browser extensions added work while the page loaded. I measured again three times in a Guest window, with no extensions: median of 99.

Possible improvements

Skills applied