Board game inventory tracker and game logger
| Game catalog | Search Board Game Geek, keep player counts, weights and cover art |
| Leaderboard | Elo rating per player, win rates, streaks, head-to-head records |
| Session log | Who played, who won, scores, mood — plus per-game custom fields |
| Achievements | Milestones detected automatically as results come in |
| Player profiles | Favourite game, nemesis, best month, Elo history |
| Blog | Session recaps with rich text and images |
Self-host it, or use the built-in support for serverless hosting on AWS for ≈$0 a month.
 |
 |
The project is vibe-coded and should be treated as such.
Claude Code wrote most of the code. My background is scientific computing with extensive AWS experience and I did this project to learn frontend coding and agent orchestration in a full-stack application.
I wanted to ensure that no data is compromised when using the AWS cloud option as it has public facing endpoints. The security model is explained here: security model.
The setup used to build it is in CLAUDE.md, with these plugins:
- superpowers — brainstorming, subagent-driven development, TDD, systematic debugging
- frontend-design — non-generic UI design guidance
- chrome-devtools-mcp — live browser inspection and automation
To install:
curl -fsSL https://raw.githubusercontent.com/Strandgaard96/mc-gamertime/main/docker-compose.yml -o docker-compose.yml
echo "ADMIN_USERNAME=admin" >> .env
echo "ADMIN_PASSWORD=<your-password>" >> .env
docker compose up -dADMIN_USERNAME/ADMIN_PASSWORD are the only required setting — they bootstrap your
first admin account on first boot. Everything else — BGG_TOKEN for game search, SMTP_* for
password-reset email, APP_BASE_URL, CORS_ALLOWED_ORIGINS, etc. — is optional with a
working default; see .env.example or the full config
reference.
Open http://localhost:4263 and log in.
For setup of remote access see HTTPS / Reverse Proxy and the security model.
Host the app on AWS serverless infrastructure, provisioned by Terraform. Everything is pay-per-request, which for regular personal use amounts to roughly $0/month — the free tier covers it. Worth choosing if you want easy remote access and experience with cloud hosting while gaining the security benefits of AWS hosted infrastructure.
An AWS account, plus Terraform, Node.js and Task installed — and a domain name you own. The domain is not optional: CloudFront needs an ACM certificate, and ACM only issues one for a domain you control.
cp infra/terraform.tfvars.example infra/terraform.tfvars
# then set: domain = "example.com"domain in infra/terraform.tfvars is the only required setting - terraform apply refuses to run without it. Everything
else (subdomain, bgg_token, alert_email, cloudfront_web_acl_arn,
extra_cors_origins, aws_region) has a working default; see
infra/terraform.tfvars.example or the full AWS
guide for what each does.
For full AWS installation instructions see: Full AWS guide →.
The security considerations for the AWS hosted app are described here: Security & privacy on AWS →.
- Frontend — React 18, Vite, TypeScript, Tailwind, TanStack Query, Recharts
- Backend — Python, FastAPI; uvicorn when self-hosted, Lambda + Mangum on AWS
- Data — embedded SQLite, or DynamoDB
- Storage — local filesystem, or S3; uploaded media is served by the app behind auth, never straight from the bucket
- Infra — Terraform, GitHub Actions, release-please
Diagram source (Mermaid)
graph LR
B["Browser"]
B -->|"self-hosted"| C["one container<br/>FastAPI, serving the React build"]
C --> SQ[("SQLite file")]
C --> FS[("local filesystem")]
B -->|"AWS"| CF["CloudFront"]
CF --> S3[("S3<br/>static bundle")]
CF --> AG["API Gateway"]
AG --> L["Lambda<br/>the same FastAPI app"]
L --> DDB[("DynamoDB")]
L --> S3M[("S3<br/>uploaded media")]
- Contributing guide
- Architecture walkthrough — how a request flows end to end
- Recipes — add an endpoint, a page, a table
- Security policy — report a vulnerability privately
0 comments
log in to comment.