Archived
CORS middleware was registered after Vapor's error middleware, so error responses went out without CORS headers and the browser reported every rejection as an opaque "Failed to fetch" — a taken handle or a wrong passphrase became undiagnosable in the client. The container healthcheck called wget, which is not in the runtime image, so it could never pass and an orchestrator would have restarted the container forever. Root-level filenames were decrypted with the session's label key, but a root listing spans labels and each entry is named under the key of its own label. A cleared user saw rows they could not read. They now use the right key per row. Also handles empty response bodies in the accounts client: a 201 with no body is an ordinary answer and calling .json() on one throws. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
16 lines
496 B
YAML
16 lines
496 B
YAML
# Development overlay. Publishes Postgres on loopback so a locally-run server
|
|
# can reach it. Never use this on a deployed host.
|
|
#
|
|
# docker compose -f docker-compose.yml -f docker-compose.dev.yml up -d db
|
|
services:
|
|
db:
|
|
ports:
|
|
- "127.0.0.1:5432:5432"
|
|
|
|
# Serve templates and static assets from the working tree, so front-end
|
|
# changes take a container restart rather than an image rebuild.
|
|
app:
|
|
volumes:
|
|
- ./Public:/app/Public:ro
|
|
- ./Resources:/app/Resources:ro
|