mirror of
https://github.com/dsec-hub/dsec-discord-bot.git
synced 2026-09-22 07:44:26 +00:00
5751be129d
- docker-compose.yml: `restart: unless-stopped` so a panic, bad frame or VPS reboot brings the bot back instead of leaving it dead. Comment explaining why no healthcheck (slim runtime, no HTTP port). - Cargo.toml: enable tracing-subscriber's env-filter feature (declared but never initialised until now). - main.rs: initialise tracing as the first statement in main(), defaulting to `info` — serenity/poise/supabase logs now surface, without leaking student IDs or the service email that the Supabase client emits at `debug`. - deploy.yml: after `up -d`, assert the container is actually Running 30s later and dump its logs and fail if not — `up -d` returns 0 on container creation, not on a working process. - Dockerfile: pin the builder to rust:1-bookworm to match the bookworm-slim runtime, removing the trixie/bookworm glibc mismatch. - README: document the info-level default and the RUST_LOG=debug PII footgun. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017XrE7F9ZuBWdQnS8CZvYDE
12 lines
No EOL
546 B
YAML
12 lines
No EOL
546 B
YAML
services:
|
|
dsec_bot:
|
|
build: .
|
|
# Bring the bot back on process exit — a panic, a bad Discord frame, or a VPS
|
|
# reboot — instead of leaving it dead until someone notices (OPS-04). No
|
|
# `healthcheck:` block: the runtime image is debian:bookworm-slim with only
|
|
# ca-certificates (no ps/curl) and the bot serves no HTTP port, so there is
|
|
# nothing to probe; `restart: unless-stopped` acts on process exit, which is
|
|
# exactly the failure mode here. Do not add one.
|
|
restart: unless-stopped
|
|
env_file:
|
|
- .env |