Prompt file imported from alanjwade/fct_stats (.github/prompts/publish_to_production.prompt.md). Copyright stays with the author.

Publishing FCT Stats to Production

Name: publish_to_production
Author: alanjwade

This prompt helps you publish the FCT Stats application to the homelab production server.

Overview

The FCT Stats application runs on a homelab server using Docker containers. There are separate publish scripts for:

Webapp: Flask application code, templates, static files
Database: SQLite database with all athlete/meet/result data
Both: Combined publish (recommended for most updates)

Quick Start (Default Command)

To publish everything and restart the production server in one go:

./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build

Or create an alias in your shell:

alias publish-prod='./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build'

Then just run: publish-prod

Publishing Options

Option 1: Publish Everything (Recommended)

Use this when you've made changes to both code and data.

./scripts/publish-all.sh

What it does:

Syncs webapp code to ~/homelab/fct_stats/ (excluding development files)
Backs up existing database to ~/homelab/fct_stats/backups/
Copies new database from data/db/fct_stats.db to homelab
Shows database statistics

Then restart the server:

cd ~/homelab/fct_stats
mkdir -p data/db
mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true
docker-compose -f docker/docker-compose.yml up -d --build

Or use the restart script:

./scripts/homelab-restart.sh

Option 2: Publish Only Webapp

Use this when you've made code/template/styling changes but no database changes.

./scripts/publish-webapp.sh

What it does:

Syncs webapp files using rsync
Excludes: venv, pycache, .git, data/db/, data/sources//pages/, data/sources/

Then restart the webapp container:

./scripts/homelab-restart.sh

Or manually:

cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml restart webapp

Option 3: Publish Only Database

Use this when you've added new meet results or updated data but code is unchanged.

./scripts/publish-db.sh

What it does:

Creates backup: ~/homelab/fct_stats/backups/fct_stats_YYYYMMDD_HHMMSS.db
Copies data/db/fct_stats.db to ~/homelab/fct_stats/data/db/
Shows statistics (athletes, events, meets, results counts)

Then restart the webapp container:

./scripts/homelab-restart.sh

Or manually:

cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml restart webapp

Option 4: Just Restart the Production Server

Use this to restart the server without publishing any changes.

./scripts/homelab-restart.sh

What it does:

Stops existing services
Rebuilds and starts fresh containers
Shows confirmation

Or manually:

cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml down
docker-compose -f docker/docker-compose.yml up -d --build

Step-by-Step Publishing Workflow

For a Typical Update (New Meet Results Added)

Ensure database is up to date:

python scripts/import_from_parsed_meets.py

Verify locally:

cd webapp
python app.py
# Visit http://localhost:5000 and check changes

Publish everything:
```
./scripts/publish-all.sh
```

Restart production services:

cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml up -d --build

Check logs for errors:

docker-compose -f docker/docker-compose.yml logs -f webapp

Visit production site:
- https://track.fchsrunning.org

For Code-Only Changes (Templates, Styling, Routes)

Test locally:
```
cd webapp
python app.py
```
Publish webapp only:
```
./scripts/publish-webapp.sh
```

Restart webapp container:

cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml restart webapp

For Data-Only Changes (New Results, Updated Records)

Import new data:

python scripts/import_from_parsed_meets.py

Publish database only:
```
./scripts/publish-db.sh
```

Restart webapp container:

cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml restart webapp

Important Notes

Database Backups

Automatic backups are created in ~/homelab/fct_stats/backups/
Format: fct_stats_YYYYMMDD_HHMMSS.db
These backups are important! The database is read-only in production

What Gets Excluded During Webapp Sync

The rsync excludes:

venv/ - Virtual environments
__pycache__/ - Python bytecode
*.pyc - Compiled Python files
.git/ - Git repository
data/db/ - Database (published separately)
data/sources/<year>/pages/ - Raw meet pages (not needed in production)
data/sources/ - YAML meet files (not needed in production)
.vscode/ - Editor config
*.log - Log files

Production Environment

Location: ~/homelab/fct_stats/
Docker Compose: docker/docker-compose.yml
URL: https://track.fchsrunning.org
Container Name: fct_stats_webapp
Network: proxy-network (shared with nginx proxy)
Database: Mounted read-only from ../data/db/fct_stats.db

Troubleshooting

Site Not Updating After Publish

Check if services are running:

cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml ps

Rebuild containers:

docker-compose -f docker/docker-compose.yml up -d --build

Check logs:

docker-compose -f docker/docker-compose.yml logs -f webapp

Database Not Found Error

Verify database is in correct location:

ls -lh ~/homelab/fct_stats/data/db/fct_stats.db

If the database is at ~/homelab/fct_stats/data/fct_stats.db, move it:

mkdir -p ~/homelab/fct_stats/data/db
mv ~/homelab/fct_stats/data/fct_stats.db ~/homelab/fct_stats/data/db/fct_stats.db

Check database permissions:

chmod 644 ~/homelab/fct_stats/data/db/fct_stats.db

Verify database is valid:

sqlite3 ~/homelab/fct_stats/data/db/fct_stats.db "SELECT COUNT(*) FROM athletes;"

Restart the container:

cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml restart webapp

Container Won't Start

Check for port conflicts:

docker-compose -f docker/docker-compose.yml ps
netstat -tulpn | grep 5000

Remove old containers:

docker-compose -f docker/docker-compose.yml down
docker-compose -f docker/docker-compose.yml up -d

Check Docker logs:
```
docker logs fct_stats_webapp
```

Quick Reference Commands

# QUICK START: Publish everything and restart (recommended)
./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build

# Or use the dedicated script
./scripts/homelab-restart.sh

# Publish everything only (without restart)
./scripts/publish-all.sh

# Publish webapp only
./scripts/publish-webapp.sh

# Publish database only
./scripts/publish-db.sh

# Restart services (after publishing separately)
./scripts/homelab-restart.sh

# Manual restart without publish
cd ~/homelab/fct_stats
docker-compose -f docker/docker-compose.yml up -d --build

# Restart just the webapp container
docker-compose -f docker/docker-compose.yml restart webapp

# Stop services
docker-compose -f docker/docker-compose.yml down

# View logs
docker-compose -f docker/docker-compose.yml logs -f

# Check status
docker-compose -f docker/docker-compose.yml ps

Pre-Publish Checklist

Local changes tested with cd webapp && python app.py
Database imported with latest data: python scripts/import_from_parsed_meets.py
No errors in local testing
Git committed (optional but recommended)
Ready to run appropriate publish script

Post-Publish Verification

Services started: docker-compose ps shows "Up"
No errors in logs: docker-compose logs webapp
Production site accessible: https://track.fchsrunning.org
New data/changes visible on production site
Database backup created (if db was published)

# Publishing FCT Stats to Production This prompt helps you publish the FCT Stats application to the homelab production server. ## Overview The FCT Stats application runs on a homelab server using Docker containers. There are separate publish scripts for: - **Webapp**: Flask application code, templates, static files - **Database**: SQLite database with all athlete/meet/result data - **Both**: Combined publish (recommended for most updates) ## Quick Start (Default Command) To publish everything and restart the production server in one go: ```bash ./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build ``` Or create an alias in your shell: ```bash alias publish-prod='./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build' ``` Then just run: `publish-prod` --- ## Publishing Options ### Option 1: Publish Everything (Recommended) Use this when you've made changes to both code and data. ```bash ./scripts/publish-all.sh ``` **What it does:** 1. Syncs webapp code to `~/homelab/fct_stats/` (excluding development files) 2. Backs up existing database to `~/homelab/fct_stats/backups/` 3. Copies new database from `data/db/fct_stats.db` to homelab 4. Shows database statistics **Then restart the server:** ```bash cd ~/homelab/fct_stats mkdir -p data/db mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true docker-compose -f docker/docker-compose.yml up -d --build ``` **Or use the restart script:** ```bash ./scripts/homelab-restart.sh ``` ### Option 2: Publish Only Webapp Use this when you've made code/template/styling changes but no database changes. ```bash ./scripts/publish-webapp.sh ``` **What it does:** - Syncs webapp files using rsync - Excludes: venv, __pycache__, .git, data/db/, data/sources/<year>/pages/, data/sources/ **Then restart the webapp container:** ```bash ./scripts/homelab-restart.sh ``` Or manually: ```bash cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml restart webapp ``` ### Option 3: Publish Only Database Use this when you've added new meet results or updated data but code is unchanged. ```bash ./scripts/publish-db.sh ``` **What it does:** 1. Creates backup: `~/homelab/fct_stats/backups/fct_stats_YYYYMMDD_HHMMSS.db` 2. Copies `data/db/fct_stats.db` to `~/homelab/fct_stats/data/db/` 3. Shows statistics (athletes, events, meets, results counts) **Then restart the webapp container:** ```bash ./scripts/homelab-restart.sh ``` Or manually: ```bash cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml restart webapp ``` ### Option 4: Just Restart the Production Server Use this to restart the server without publishing any changes. ```bash ./scripts/homelab-restart.sh ``` **What it does:** 1. Stops existing services 2. Rebuilds and starts fresh containers 3. Shows confirmation Or manually: ```bash cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml down docker-compose -f docker/docker-compose.yml up -d --build ``` ## Step-by-Step Publishing Workflow ### For a Typical Update (New Meet Results Added) 1. **Ensure database is up to date:** ```bash python scripts/import_from_parsed_meets.py ``` 2. **Verify locally:** ```bash cd webapp python app.py # Visit http://localhost:5000 and check changes ``` 3. **Publish everything:** ```bash ./scripts/publish-all.sh ``` 4. **Restart production services:** ```bash cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml up -d --build ``` 5. **Check logs for errors:** ```bash docker-compose -f docker/docker-compose.yml logs -f webapp ``` 6. **Visit production site:** - https://track.fchsrunning.org ### For Code-Only Changes (Templates, Styling, Routes) 1. **Test locally:** ```bash cd webapp python app.py ``` 2. **Publish webapp only:** ```bash ./scripts/publish-webapp.sh ``` 3. **Restart webapp container:** ```bash cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml restart webapp ``` ### For Data-Only Changes (New Results, Updated Records) 1. **Import new data:** ```bash python scripts/import_from_parsed_meets.py ``` 2. **Publish database only:** ```bash ./scripts/publish-db.sh ``` 3. **Restart webapp container:** ```bash cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml restart webapp ``` ## Important Notes ### Database Backups - Automatic backups are created in `~/homelab/fct_stats/backups/` - Format: `fct_stats_YYYYMMDD_HHMMSS.db` - **These backups are important!** The database is read-only in production ### What Gets Excluded During Webapp Sync The rsync excludes: - `venv/` - Virtual environments - `__pycache__/` - Python bytecode - `*.pyc` - Compiled Python files - `.git/` - Git repository - `data/db/` - Database (published separately) - `data/sources/<year>/pages/` - Raw meet pages (not needed in production) - `data/sources/` - YAML meet files (not needed in production) - `.vscode/` - Editor config - `*.log` - Log files ### Production Environment - **Location**: `~/homelab/fct_stats/` - **Docker Compose**: `docker/docker-compose.yml` - **URL**: https://track.fchsrunning.org - **Container Name**: `fct_stats_webapp` - **Network**: `proxy-network` (shared with nginx proxy) - **Database**: Mounted read-only from `../data/db/fct_stats.db` ## Troubleshooting ### Site Not Updating After Publish 1. **Check if services are running:** ```bash cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml ps ``` 2. **Rebuild containers:** ```bash docker-compose -f docker/docker-compose.yml up -d --build ``` 3. **Check logs:** ```bash docker-compose -f docker/docker-compose.yml logs -f webapp ``` ### Database Not Found Error 1. **Verify database is in correct location:** ```bash ls -lh ~/homelab/fct_stats/data/db/fct_stats.db ``` If the database is at `~/homelab/fct_stats/data/fct_stats.db`, move it: ```bash mkdir -p ~/homelab/fct_stats/data/db mv ~/homelab/fct_stats/data/fct_stats.db ~/homelab/fct_stats/data/db/fct_stats.db ``` 2. **Check database permissions:** ```bash chmod 644 ~/homelab/fct_stats/data/db/fct_stats.db ``` 3. **Verify database is valid:** ```bash sqlite3 ~/homelab/fct_stats/data/db/fct_stats.db "SELECT COUNT(*) FROM athletes;" ``` 4. **Restart the container:** ```bash cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml restart webapp ``` ### Container Won't Start 1. **Check for port conflicts:** ```bash docker-compose -f docker/docker-compose.yml ps netstat -tulpn | grep 5000 ``` 2. **Remove old containers:** ```bash docker-compose -f docker/docker-compose.yml down docker-compose -f docker/docker-compose.yml up -d ``` 3. **Check Docker logs:** ```bash docker logs fct_stats_webapp ``` ## Quick Reference Commands ```bash # QUICK START: Publish everything and restart (recommended) ./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build # Or use the dedicated script ./scripts/homelab-restart.sh # Publish everything only (without restart) ./scripts/publish-all.sh # Publish webapp only ./scripts/publish-webapp.sh # Publish database only ./scripts/publish-db.sh # Restart services (after publishing separately) ./scripts/homelab-restart.sh # Manual restart without publish cd ~/homelab/fct_stats docker-compose -f docker/docker-compose.yml up -d --build # Restart just the webapp container docker-compose -f docker/docker-compose.yml restart webapp # Stop services docker-compose -f docker/docker-compose.yml down # View logs docker-compose -f docker/docker-compose.yml logs -f # Check status docker-compose -f docker/docker-compose.yml ps ``` ## Pre-Publish Checklist - [ ] Local changes tested with `cd webapp && python app.py` - [ ] Database imported with latest data: `python scripts/import_from_parsed_meets.py` - [ ] No errors in local testing - [ ] Git committed (optional but recommended) - [ ] Ready to run appropriate publish script ## Post-Publish Verification - [ ] Services started: `docker-compose ps` shows "Up" - [ ] No errors in logs: `docker-compose logs webapp` - [ ] Production site accessible: https://track.fchsrunning.org - [ ] New data/changes visible on production site - [ ] Database backup created (if db was published)

{ "prompt": "# Publishing FCT Stats to Production\n\nThis prompt helps you publish the FCT Stats application to the homelab production server.\n\n## Overview\n\nThe FCT Stats application runs on a homelab server using Docker containers. There are separate publish scripts for:\n- **Webapp**: Flask application code, templates, static files\n- **Database**: SQLite database with all athlete/meet/result data\n- **Both**: Combined publish (recommended for most updates)\n\n## Quick Start (Default Command)\n\nTo publish everything and restart the production server in one go:\n\n```bash\n./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build\n```\n\nOr create an alias in your shell:\n```bash\nalias publish-prod='./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build'\n```\n\nThen just run: `publish-prod`\n\n---\n\n## Publishing Options\n\n### Option 1: Publish Everything (Recommended)\nUse this when you've made changes to both code and data.\n\n```bash\n./scripts/publish-all.sh\n```\n\n**What it does:**\n1. Syncs webapp code to `~/homelab/fct_stats/` (excluding development files)\n2. Backs up existing database to `~/homelab/fct_stats/backups/`\n3. Copies new database from `data/db/fct_stats.db` to homelab\n4. Shows database statistics\n\n**Then restart the server:**\n```bash\ncd ~/homelab/fct_stats\nmkdir -p data/db\nmv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true\ndocker-compose -f docker/docker-compose.yml up -d --build\n```\n\n**Or use the restart script:**\n```bash\n./scripts/homelab-restart.sh\n```\n\n### Option 2: Publish Only Webapp\nUse this when you've made code/template/styling changes but no database changes.\n\n```bash\n./scripts/publish-webapp.sh\n```\n\n**What it does:**\n- Syncs webapp files using rsync\n- Excludes: venv, __pycache__, .git, data/db/, data/sources/<year>/pages/, data/sources/\n\n**Then restart the webapp container:**\n```bash\n./scripts/homelab-restart.sh\n```\n\nOr manually:\n```bash\ncd ~/homelab/fct_stats\ndocker-compose -f docker/docker-compose.yml restart webapp\n```\n\n### Option 3: Publish Only Database\nUse this when you've added new meet results or updated data but code is unchanged.\n\n```bash\n./scripts/publish-db.sh\n```\n\n**What it does:**\n1. Creates backup: `~/homelab/fct_stats/backups/fct_stats_YYYYMMDD_HHMMSS.db`\n2. Copies `data/db/fct_stats.db` to `~/homelab/fct_stats/data/db/`\n3. Shows statistics (athletes, events, meets, results counts)\n\n**Then restart the webapp container:**\n```bash\n./scripts/homelab-restart.sh\n```\n\nOr manually:\n```bash\ncd ~/homelab/fct_stats\ndocker-compose -f docker/docker-compose.yml restart webapp\n```\n\n### Option 4: Just Restart the Production Server\nUse this to restart the server without publishing any changes.\n\n```bash\n./scripts/homelab-restart.sh\n```\n\n**What it does:**\n1. Stops existing services\n2. Rebuilds and starts fresh containers\n3. Shows confirmation\n\nOr manually:\n```bash\ncd ~/homelab/fct_stats\ndocker-compose -f docker/docker-compose.yml down\ndocker-compose -f docker/docker-compose.yml up -d --build\n```\n\n## Step-by-Step Publishing Workflow\n\n### For a Typical Update (New Meet Results Added)\n\n1. **Ensure database is up to date:**\n ```bash\n python scripts/import_from_parsed_meets.py\n ```\n\n2. **Verify locally:**\n ```bash\n cd webapp\n python app.py\n # Visit http://localhost:5000 and check changes\n ```\n\n3. **Publish everything:**\n ```bash\n ./scripts/publish-all.sh\n ```\n\n4. **Restart production services:**\n ```bash\n cd ~/homelab/fct_stats\n docker-compose -f docker/docker-compose.yml up -d --build\n ```\n\n5. **Check logs for errors:**\n ```bash\n docker-compose -f docker/docker-compose.yml logs -f webapp\n ```\n\n6. **Visit production site:**\n - https://track.fchsrunning.org\n\n### For Code-Only Changes (Templates, Styling, Routes)\n\n1. **Test locally:**\n ```bash\n cd webapp\n python app.py\n ```\n\n2. **Publish webapp only:**\n ```bash\n ./scripts/publish-webapp.sh\n ```\n\n3. **Restart webapp container:**\n ```bash\n cd ~/homelab/fct_stats\n docker-compose -f docker/docker-compose.yml restart webapp\n ```\n\n### For Data-Only Changes (New Results, Updated Records)\n\n1. **Import new data:**\n ```bash\n python scripts/import_from_parsed_meets.py\n ```\n\n2. **Publish database only:**\n ```bash\n ./scripts/publish-db.sh\n ```\n\n3. **Restart webapp container:**\n ```bash\n cd ~/homelab/fct_stats\n docker-compose -f docker/docker-compose.yml restart webapp\n ```\n\n## Important Notes\n\n### Database Backups\n- Automatic backups are created in `~/homelab/fct_stats/backups/`\n- Format: `fct_stats_YYYYMMDD_HHMMSS.db`\n- **These backups are important!** The database is read-only in production\n\n### What Gets Excluded During Webapp Sync\nThe rsync excludes:\n- `venv/` - Virtual environments\n- `__pycache__/` - Python bytecode\n- `*.pyc` - Compiled Python files\n- `.git/` - Git repository\n- `data/db/` - Database (published separately)\n- `data/sources/<year>/pages/` - Raw meet pages (not needed in production)\n- `data/sources/` - YAML meet files (not needed in production)\n- `.vscode/` - Editor config\n- `*.log` - Log files\n\n### Production Environment\n- **Location**: `~/homelab/fct_stats/`\n- **Docker Compose**: `docker/docker-compose.yml`\n- **URL**: https://track.fchsrunning.org\n- **Container Name**: `fct_stats_webapp`\n- **Network**: `proxy-network` (shared with nginx proxy)\n- **Database**: Mounted read-only from `../data/db/fct_stats.db`\n\n## Troubleshooting\n\n### Site Not Updating After Publish\n\n1. **Check if services are running:**\n ```bash\n cd ~/homelab/fct_stats\n docker-compose -f docker/docker-compose.yml ps\n ```\n\n2. **Rebuild containers:**\n ```bash\n docker-compose -f docker/docker-compose.yml up -d --build\n ```\n\n3. **Check logs:**\n ```bash\n docker-compose -f docker/docker-compose.yml logs -f webapp\n ```\n\n### Database Not Found Error\n\n1. **Verify database is in correct location:**\n ```bash\n ls -lh ~/homelab/fct_stats/data/db/fct_stats.db\n ```\n \n If the database is at `~/homelab/fct_stats/data/fct_stats.db`, move it:\n ```bash\n mkdir -p ~/homelab/fct_stats/data/db\n mv ~/homelab/fct_stats/data/fct_stats.db ~/homelab/fct_stats/data/db/fct_stats.db\n ```\n\n2. **Check database permissions:**\n ```bash\n chmod 644 ~/homelab/fct_stats/data/db/fct_stats.db\n ```\n\n3. **Verify database is valid:**\n ```bash\n sqlite3 ~/homelab/fct_stats/data/db/fct_stats.db \"SELECT COUNT(*) FROM athletes;\"\n ```\n\n4. **Restart the container:**\n ```bash\n cd ~/homelab/fct_stats\n docker-compose -f docker/docker-compose.yml restart webapp\n ```\n\n### Container Won't Start\n\n1. **Check for port conflicts:**\n ```bash\n docker-compose -f docker/docker-compose.yml ps\n netstat -tulpn | grep 5000\n ```\n\n2. **Remove old containers:**\n ```bash\n docker-compose -f docker/docker-compose.yml down\n docker-compose -f docker/docker-compose.yml up -d\n ```\n\n3. **Check Docker logs:**\n ```bash\n docker logs fct_stats_webapp\n ```\n\n## Quick Reference Commands\n\n```bash\n# QUICK START: Publish everything and restart (recommended)\n./scripts/publish-all.sh && cd ~/homelab/fct_stats && mkdir -p data/db && mv data/fct_stats.db data/db/fct_stats.db 2>/dev/null || true && docker-compose -f docker/docker-compose.yml up -d --build\n\n# Or use the dedicated script\n./scripts/homelab-restart.sh\n\n# Publish everything only (without restart)\n./scripts/publish-all.sh\n\n# Publish webapp only\n./scripts/publish-webapp.sh\n\n# Publish database only\n./scripts/publish-db.sh\n\n# Restart services (after publishing separately)\n./scripts/homelab-restart.sh\n\n# Manual restart without publish\ncd ~/homelab/fct_stats\ndocker-compose -f docker/docker-compose.yml up -d --build\n\n# Restart just the webapp container\ndocker-compose -f docker/docker-compose.yml restart webapp\n\n# Stop services\ndocker-compose -f docker/docker-compose.yml down\n\n# View logs\ndocker-compose -f docker/docker-compose.yml logs -f\n\n# Check status\ndocker-compose -f docker/docker-compose.yml ps\n```\n\n## Pre-Publish Checklist\n\n- [ ] Local changes tested with `cd webapp && python app.py`\n- [ ] Database imported with latest data: `python scripts/import_from_parsed_meets.py`\n- [ ] No errors in local testing\n- [ ] Git committed (optional but recommended)\n- [ ] Ready to run appropriate publish script\n\n## Post-Publish Verification\n\n- [ ] Services started: `docker-compose ps` shows \"Up\"\n- [ ] No errors in logs: `docker-compose logs webapp`\n- [ ] Production site accessible: https://track.fchsrunning.org\n- [ ] New data/changes visible on production site\n- [ ] Database backup created (if db was published)", "variables": [], "notes": "This prompt provides detailed instructions for publishing the FCT Stats application to the homelab production server. It covers various publishing options (webapp, database, combined), step-by-step workflows, troubleshooting tips, and important notes about the production environment.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/alanjwade/fct_stats", "path": ".github/prompts/publish_to_production.prompt.md", "ref": "471038e09b2d914f66d89ba6ea0f1dfdc0089e25", "url": "https://github.com/alanjwade/fct_stats/blob/471038e09b2d914f66d89ba6ea0f1dfdc0089e25/.github/prompts/publish_to_production.prompt.md", "key": "alanjwade/fct_stats/.github/prompts/publish_to_production.prompt.md" } }, "model_hints": [ "GPT-4o (copilot)" ] }

publish_to_production

About

Publishing FCT Stats to Production

Overview

Quick Start (Default Command)

Publishing Options

Option 1: Publish Everything (Recommended)

Option 2: Publish Only Webapp

Option 3: Publish Only Database

Option 4: Just Restart the Production Server

Step-by-Step Publishing Workflow

For a Typical Update (New Meet Results Added)

For Code-Only Changes (Templates, Styling, Routes)

For Data-Only Changes (New Results, Updated Records)

Important Notes

Database Backups

What Gets Excluded During Webapp Sync

Production Environment

Troubleshooting

Site Not Updating After Publish

Database Not Found Error

Container Won't Start

Quick Reference Commands

Pre-Publish Checklist

Post-Publish Verification

Use it

Manifest

Reviews