6ac814475e
Everything on this site so far has been a file built from git. This is the first component that runs code to answer a request and the first whose data git does not hold, so the trade is stated in the README and the backup script is not optional. Roles are owner, admin and user. The owner is seeded once from BOARD_OWNER and cannot be seeded again, because otherwise editing a compose file would be a quieter way to take the top role than asking for it; ownership moves only by transfer, inside the app. There is exactly one owner and a partial unique index enforces it, so the invariant holds even when a handler is wrong. The owner is beyond suspension and demotion by everyone, themselves included. Only the owner makes admins; admins make users. Sign-in goes through Gitea as a confidential OAuth client — the opposite of Decap, which has to be public because it runs in the browser. The rule the whole thing rests on is that a Gitea account is not a membership: entry needs an active row in `members`, or every account on the instance is a member, starting with the translations bot. Admins can delete any post; nobody can edit anyone else's, admins included. Taking a post down is visible to its author. Quietly rewriting it is not, and an admin who could do that could leave a sentence attributed to someone who never wrote it. The plan said admins could do both; this is the one place the implementation departs from it. Markdown renders with raw HTML disabled, which is the entire XSS defence and the reason there is no sanitiser: the renderer emits only its own tags and escapes the rest. The CSP carries no 'unsafe-inline', which makes an inline onsubmit silently inert rather than broken, so the confirmation dialogs live in a static file and a test fails any template that grows an inline handler. GDPR is in scope rather than deferred: erasure removes the member row and moves their authorship to a tombstone so the conversations around them still read, and any member can download their own writing. Verified: 63 checks pass, covering the membership gate, every role predicate, a direct insert of a second owner being refused by the index, atomic ownership transfer, CSRF, an offsite login redirect, script tags rendering as text, soft deletes leaving both listings and exports, and the member screens rendering for each role. Smoke-tested live: headers, both static assets, and the bare /comunidad redirect that the Caddy matcher has to cover. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NizVpJ2dwzCbjCrTLCjeHn
41 lines
1.4 KiB
Docker
41 lines
1.4 KiB
Docker
# Runtime image for the members area.
|
|
#
|
|
# Thin, like docker/translate/Dockerfile: no build tooling, no compiler, and
|
|
# nothing in it that is not needed to answer a request.
|
|
#
|
|
# Build on the server, from the repository root so the app is in context:
|
|
# docker build -t vienalatina/board:1 -f docker/board/Dockerfile .
|
|
|
|
FROM python:3.12-slim
|
|
|
|
# Runs as a non-root user with the uid the host data directory is chowned to.
|
|
# Two reasons, and the second is the one that bites: root in the container
|
|
# writes root-owned files into the mounted volume, and then backups and
|
|
# manual inspection from the host need sudo for no good reason.
|
|
RUN useradd --uid 1000 --create-home --shell /usr/sbin/nologin board
|
|
|
|
WORKDIR /srv
|
|
|
|
COPY apps/board/requirements.txt /srv/requirements.txt
|
|
RUN pip install --no-cache-dir -r /srv/requirements.txt
|
|
|
|
COPY apps /srv/apps
|
|
|
|
ENV BOARD_DB=/data/board.db \
|
|
PYTHONUNBUFFERED=1
|
|
|
|
USER board
|
|
EXPOSE 8080
|
|
|
|
# Two workers is plenty for a group this size and keeps the footprint near
|
|
# 60-80MB, which is what the CX22 can spare alongside Gitea, Woodpecker and a
|
|
# translation run. --timeout is short because every request here is a SQLite
|
|
# read or write; anything slower than this is stuck, not busy.
|
|
CMD ["gunicorn", \
|
|
"--bind", "0.0.0.0:8080", \
|
|
"--workers", "2", \
|
|
"--timeout", "30", \
|
|
"--access-logfile", "-", \
|
|
"--error-logfile", "-", \
|
|
"apps.board.wsgi:application"]
|