dc50b4bcd5
The notes existed but there was nowhere to write them: a CLI command on a laptop, a tool call through Claude, or a file in a Docker volume. None of those is reachable from a phone in a lesson, which is where notes are actually taken. So: `/app`, served only when WEB_PASSWORD is set. A login, the day's notes, and a settings page for the Schulcloud token — the one surface here meant for a person rather than a program. The shape follows how the notes are written: one note per school day, one `##` heading per lesson, prose and lists and tables beneath. That turns out to be the design decision that matters, twice over. First, it is what lets WebUntis earn its keep. Opening a day with no note fills in that day's lessons — numbered, with times, teacher and room, cancellations dropped and substitutions marked. Retyping the timetable is exactly the work the second upstream exists to avoid, and "Stunden ergänzen" tops up a note started before the day ended without touching what is already written. Second, it changes how notes are indexed. A day note is indexed per lesson, not whole: search answers "my own note, Deutsch, 18.09.2026" rather than "my own note, Friday", and `list_notes subject=Deutsch` finds a day whose frontmatter names no subject at all. Indexed whole, every hit would read as a weekday and "what did we do in Deutsch" would match notes whose other five lessons were something else. `lessonHeading` and `subjectFromHeading` are a loop — the app writes the heading, the indexer reads the subject back out — and a test holds them to it. Notes taken in a lesson cannot be retaken, so the editor is built around not losing them: autosave, every keystroke mirrored to local storage, a save when the phone locks, and a fallback to the local copy when the request never arrives. A save that would overwrite a version the editor never saw is refused and the choice handed back — the notes folder is synced and open in more than one place, and a phone must not silently win over a laptop. `replaceNote` is separate from `writeNote` for that reason: never-overwrite is right for `add_note` and exactly wrong for an editor. WEB_PASSWORD is the first credential here a human types, so it is the first that can be guessed: scrypt at startup, never stored or compared in the clear, per-address rate limiting — which is not decoration, since the scrypt cost is itself a denial-of-service vector without it. The session is a signed HttpOnly SameSite=Strict cookie whose key is derived from the password, so changing it logs everyone out and there is no second secret to keep. It opens /api, because a session is the user, and never /mcp, because nothing in a browser speaks MCP. Also here, because the app made them matter: frontmatter now reads the indented `- item` list form editors write, so an Obsidian vault round-trips its tags; and a four-digit folder is a filing scheme, not a subject, so `2026/` does not file a school year under one. 357 tests; 106/107 smoke against the local instance, the one failure being the H5P service that instance does not run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
56 lines
2.0 KiB
Caddyfile
56 lines
2.0 KiB
Caddyfile
# Add this to the Pi's existing Caddyfile.
|
|
#
|
|
# Caddy obtains and renews the certificate automatically, provided the VPS
|
|
# forwards ports 80 and 443 through to this Caddy and the DNS name resolves to
|
|
# the VPS's public address.
|
|
#
|
|
# The bearer-token check lives in the application, not here: Caddy would have
|
|
# to be reloaded to rotate the token, whereas the app reads it from the
|
|
# environment. Caddy's job is TLS, timeouts and keeping the container off the
|
|
# public interface.
|
|
|
|
mcp.example.org {
|
|
encode zstd gzip
|
|
|
|
# `schulcloud-mcp` is the Compose service name; Docker's embedded DNS
|
|
# resolves it on the shared network. No host port is published. One proxy
|
|
# serves all three surfaces: /mcp for Claude, /api for the CLI, and /app for
|
|
# the notes app in a browser.
|
|
#
|
|
# Caddy sets X-Forwarded-Proto on its own, and the app needs it: the hop to
|
|
# the container is plain HTTP, so that header is the only evidence the
|
|
# session cookie may be marked Secure. Do not strip it.
|
|
reverse_proxy schulcloud-mcp:8080 {
|
|
# MCP's Streamable HTTP transport keeps a server-sent-events channel
|
|
# open for server-initiated messages. Without flush_interval -1 Caddy
|
|
# buffers those, and the connector appears to hang.
|
|
flush_interval -1
|
|
|
|
# Long enough for a full re-crawl (~270 upstream requests) and for the
|
|
# CLI streaming large files out of the mirror.
|
|
transport http {
|
|
read_timeout 600s
|
|
write_timeout 600s
|
|
}
|
|
}
|
|
|
|
header {
|
|
Strict-Transport-Security "max-age=31536000; includeSubDomains"
|
|
X-Content-Type-Options "nosniff"
|
|
Referrer-Policy "no-referrer"
|
|
-Server
|
|
}
|
|
|
|
log {
|
|
output file /var/log/caddy/schulcloud-mcp.log
|
|
# With MCP_PATH_SECRET set, a request path *is* a credential: claude.ai
|
|
# reaches the server at /<secret>/mcp. The filter rewrites that segment
|
|
# before the entry is written. The Authorization header must never reach
|
|
# disk either; Caddy does not log headers by default — do not add them.
|
|
format filter {
|
|
request>uri regexp ^/[A-Za-z0-9_-]{32,}/mcp /<secret>/mcp
|
|
wrap json
|
|
}
|
|
}
|
|
}
|