Wedding photo upload + album
- Python 62%
- HTML 38%
| app | ||
| deploy | ||
| static | ||
| .gitignore | ||
| README.md | ||
| requirements.txt | ||
Wedding Photos
Family photo & video sharing site for wedding.beckingham.dev.
Photos and videos uploaded by family are stored in Hetzner Object Storage
(S3-compatible) and served back through a small FastAPI service. Originals are
kept untouched; WebP previews/thumbnails (via vips) and H.264 web-playable
video (via ffmpeg) are generated on upload.
Stack
- App: FastAPI + uvicorn (Python 3.11)
- Storage: Hetzner Object Storage bucket
beckinghambucket(region fsn1) via MinIO provider inbeckingham-infra/object-storage - Index: SQLite at
/var/lib/wedding/index.db - Media processing:
vips(photos → webp) andffmpeg(video → mp4/poster) - Serving: Caddy → 127.0.0.1:8000
Deploy (beckingham-web)
# 1. install system deps
apt-get install -y ffmpeg libvips42 libvips-tools libheif1 python3-venv
# 2. app
mkdir -p /srv/wedding-site && cd /srv/wedding-site
git clone ... .
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
# 3. secrets (/etc/wedding/env, chmod 600)
S3_ACCESS_KEY=...
S3_SECRET_KEY=...
S3_REGION=fsn1
S3_BUCKET=beckinghambucket
WEDDING_ADMIN_PASS=...
S3_ENDPOINT=fsn1.your-objectstorage.com
# 4. systemd
install -m 644 deploy/wedding.service /etc/systemd/system/
systemctl daemon-reload && systemctl enable --now wedding
# 5. Caddy (deploy/wedding.caddy appended to Caddyfile)
# DNS: wedding.beckingham.dev A -> 178.105.225.210
API
POST /api/upload— multipartfile+uploaderGET /api/photos— JSON indexGET /api/status— countersDELETE /api/photos/{id}— needsX-Admin-Pass/f/{thumb|large|poster|play}/{id}— derived asset/o/{id}/{name}— original download