SQLite replaces Postgres, and two fixes from using the thing.
- The database is a file under ./storage instead of a second container. Ten
members never needed a database server, and the driver is pure Go, so the
build stays CGO_ENABLED=0 and the dependency count is unchanged. One bind
mount is now the whole backup: no pgdata, no healthcheck-gated depends_on,
no startup retry loop. Timestamps are UTC text, idle_ttl is seconds, the
divisive/unified boards carry their own stddev, and foreign keys are on by
pragma. Tests get a database file each and run without any setup
- Invites are copied, not clicked. An invite is something to send, and the
anchor opened the join form in the admin's own browser
- Feedback asks for more than faults: the footer reads "Ongelmia? Ideoita?
Palautetta?" and the page behind it invites ideas rather than only bugs
- Kuuntele YouTubessa opens in a new tab, so a half-typed review survives it
Step 2 of the build order. The admin mints an invite link, the recipient
registers with it, and from then on has a session.
- The invite is spent in the same transaction that creates the account, so a
failed signup leaves the code usable
- Sessions are idle timeouts, 24h or 30 days with remember me, read from a
cookie or a bearer header, extended at most once a minute
- Ban is a reversible toggle that drops the member's live sessions
- No password minimum; login is rate limited instead, 10 failures per email
in 15 minutes, cleared by a correct password
- Invite codes render as links carrying ?code=, which the register form
prefills; PUBLIC_URL makes them pasteable from the loopback admin panel
Tests cover invite spending, the idle timeout, ban, and the rate limiter.
Esa Kataja