Remove dead code identified in docs/SANITIZATION-REVIEW.md:
- app/blueprints/content_old.py and app/blueprints/playlist.py
- app/models/group.py, app/utils/nginx_config_reader.py
- orphaned templates (content_list, edit_content, upload_content,
player_page) and the related group/Template references
Result: 6 blueprints, 82 routes, no dead modules or orphan templates.
Add files that deploy.sh and docker-entrypoint.sh already require but
which were never tracked:
- https_manager.py (referenced by deploy.sh, migrate_network.sh,
docker-entrypoint.sh)
- Caddyfile.example (seeded by deploy.sh; its absence aborts deploy)
Relocate generated Graphify artifacts from graphify-out/ to
docs/graphify-out/ (110 files, no content change) and archive the
superseded docs under docs/.
Ignore hygiene:
- ignore ad-hoc .env backups (.env.bak*) — they contain live secrets
- keep the pre-sanitization snapshots (docs/legacy code/,
docs/old_code_documentation/) on disk but out of the repo
Fix .env.example: drop a duplicated config block, genericize the
hardcoded host IP, and document HOSTNAME_INTERNAL.
- Implement Docker image-based deployment (Option 1)
* Code immutable in image, no volume override
* Eliminated init-data.sh manual step
* Simplified deployment process
- Unified persistence in data/ folder
* Moved nginx.conf and nginx-custom-domains.conf to data/
* All runtime configs and data in single location
* Clear separation: repo (source) vs data/ (runtime)
- Archive legacy features
* Groups blueprint and templates removed
* Legacy playlist routes redirected to content area
* Organized in old_code_documentation/
- Added network migration support
* New migrate_network.sh script for IP changes
* Regenerates SSL certs for new IP
* Updates database configuration
* Tested workflow: clone → deploy → migrate
- Enhanced deploy.sh
* Creates data directories
* Copies nginx configs from repo to data/
* Validates file existence before deployment
* Prevents incomplete deployments
- Updated documentation
* QUICK_DEPLOYMENT.md shows 4-step workflow
* Complete deployment workflow documented
* Migration procedures included
- Production ready deployment workflow:
1. Clone & setup (.env configuration)
2. Deploy (./deploy.sh)
3. Migrate network (./migrate_network.sh if needed)
4. Normal operations (docker compose restart)
- Enhanced Caddyfile with consolidated HTTPS block supporting all access points
- Added support for https://digiserver, https://10.76.152.164, and https://digiserver.sibiusb.harting.intra
- Configured Caddy reverse proxy with HTTP/3 (QUIC), TLS 1.3+, and HTTP/2 support
- Implemented security headers (X-Frame-Options, X-Content-Type-Options, X-XSS-Protection)
- Added HTTP to HTTPS automatic redirects for all endpoints
- Enhanced setup_https.sh with improved error handling and progress reporting
- Created deploy.sh for fully automated one-command deployment
- Added comprehensive deployment documentation (5 guides)
- Configured 2GB file upload limit and 300s request/response timeouts
- Added Caddy admin API on port 2019 for configuration management
- Implemented health checks and container dependency management
- All volumes persistent and properly isolated
- Production-ready configuration with environment variable parameterization
ske087
Deployment System
DigiServer Admin
Quality App Developer