- Create frontend-sba/.env.example and frontend-pd/.env.example templates - Fix hardcoded allowedHosts in nuxt.config.ts (now reads NUXT_ALLOWED_HOSTS) - Add NUXT_ALLOWED_HOSTS support to frontend-pd/nuxt.config.ts - Update docker-compose.yml with missing env vars: - FRONTEND_URL, DISCORD_SERVER_REDIRECT_URI - ALLOWED_DISCORD_IDS, WS_HEARTBEAT_INTERVAL, WS_CONNECTION_TIMEOUT - NUXT_ALLOWED_HOSTS for both frontends - Create docker-compose.prod.yml for production overrides - Update root .env.example with new variables - Add "Multi-Domain Deployment" section to README.md with checklist - Update all CLAUDE.md files with environment configuration docs - Remove obsolete 'version' attribute from docker-compose files 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .claude | ||
| .git-hooks | ||
| alembic | ||
| app | ||
| scripts | ||
| terminal_client | ||
| tests | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| .python-version | ||
| alembic.ini | ||
| CLAUDE.md | ||
| clean_test_data.py | ||
| docker-compose.yml | ||
| Dockerfile | ||
| mypy.ini | ||
| pyproject.toml | ||
| pyrightconfig.json | ||
| pytest.ini | ||
| README.md | ||
| requirements-dev.txt | ||
| requirements.txt | ||
| TEST_COVERAGE_SUMMARY.md | ||
| test_db_playground.py | ||
| test_pd_api_live.py | ||
| test_pd_api_mock.py | ||
| test_redis_cache.py | ||
| uv.lock | ||
Paper Dynasty Backend
FastAPI-based real-time baseball game engine with WebSocket support.
Quick Start
# Install UV
curl -LsSf https://astral.sh/uv/install.sh | sh
# Install dependencies
uv sync
# Apply database migrations
uv run alembic upgrade head
# Run server
uv run python -m app.main
Database Migrations
This project uses Alembic for database schema migrations.
Initial Setup (New Database)
# Apply all migrations to create schema
uv run alembic upgrade head
Creating New Migrations
# Auto-generate from model changes
uv run alembic revision --autogenerate -m "Description of changes"
# IMPORTANT: Always review the generated migration before applying!
# Then apply:
uv run alembic upgrade head
Viewing Migration Status
# Show migration history
uv run alembic history
# Show current revision
uv run alembic current
Rolling Back
# Rollback one migration
uv run alembic downgrade -1
# Rollback to specific revision
uv run alembic downgrade 001
# Rollback all (dangerous!)
uv run alembic downgrade base
Migration Best Practices
- Always review auto-generated migrations before applying - autogenerate is helpful but not perfect
- Test migrations on dev/staging before production
- Keep migrations small and focused - easier to rollback
- Never edit migrations that have been applied to shared databases
- Include both upgrade and downgrade for reversibility
Existing Migrations
| Revision | Description |
|---|---|
| 001 | Initial schema (games, plays, lineups, rolls, etc.) |
| 004 | Materialized views for statistics |
Documentation
See CLAUDE.md for full documentation.