Archived Documentation¶
This folder contains documentation that is no longer current but kept for historical reference.
Why These Docs Were Archived¶
All documents in this folder relate to the Uplink 2.0 upgrade, which was completed on February 24, 2026.
What Was Accomplished¶
The production server (uplink.sensational.systems) now runs: - ✅ Docker containers (web, daphne, huey, redis, nginx, certbot) - ✅ Python 3.9 with uv package manager - ✅ gunicorn production web server - ✅ nginx reverse proxy with SSL/HTTPS - ✅ Let's Encrypt SSL certificates (auto-renewal) - ✅ DEBUG=False (production mode) - ✅ PrestaShop sync via Docker cron jobs
Archived Files¶
ROLLBACK.md¶
Status: ❌ Outdated
Created: February 2, 2026
Superseded by: Docker is now in production, no rollback needed
What it was: Guide for rolling back from Docker to pipenv during the initial Docker testing phase.
Why archived: - Written when Docker was "development-only" - Production now successfully runs on Docker - Pipenv is no longer used in production - Rollback to pipenv is not a viable production option
Historical value: Shows the cautious approach taken during Docker migration, with clear safety nets and rollback procedures.
DOCKER_SETUP_GUIDE.md¶
Status: ❌ Outdated
Created: February 2, 2026
Superseded by: ../deployment/DOCKER_DEPLOYMENT.md and ../deployment/ServerSetupLog.md
What it was: Comprehensive step-by-step guide for initial Docker setup, covering development environment, production deployment, and maintenance procedures.
Why archived: - Written as a prospective guide before actual deployment - Actual deployment process documented in ServerSetupLog.md - Current deployment procedures are in DOCKER_DEPLOYMENT.md - Setup is already complete in production
Historical value: Shows the detailed planning and testing approach used during Docker migration. Useful for understanding the thought process, but actual procedures differed in practice.
PRODUCTION_DOCKER_MIGRATION.md¶
Status: ✅ Completed
Superseded by: ../deployment/DOCKER_DEPLOYMENT.md
What it was: Step-by-step guide for migrating from pipenv to Docker on the production server.
Why archived: Migration completed successfully. The actual steps taken are documented in:
- ../deployment/ServerSetupLog.md - Detailed log of what was actually done
- ../deployment/Uplink2.0_UpgradeLogs.md - Summary of changes
Current deployment process: See ../deployment/DOCKER_DEPLOYMENT.md
UBUNTU_24_FRESH_SETUP.md¶
Status: ✅ Completed
Superseded by: ../deployment/DOCKER_DEPLOYMENT.md - Section 3: "New Server Setup"
What it was: Guide for setting up Uplink on a fresh Ubuntu 24.04 VM with parallel operation strategy.
Why archived: New server (uplink) setup completed successfully using Docker. The actual setup process is documented in ../deployment/ServerSetupLog.md.
Setting up new servers now: Use ../deployment/DOCKER_DEPLOYMENT.md - includes disaster recovery procedure.
Uplink2.0_PLAN.md¶
Status: ✅ Completed (Phase 1)
What's next: Phase 2+ deferred or reprioritized
What it was: Comprehensive plan for upgrading Uplink infrastructure: - Phase 1: Docker + uv ✅ DONE - Phase 2: Python/Django upgrades ⏸️ Deferred - Phase 3: nginx ✅ DONE (completed as part of Docker) - Phase 4: systemd ✅ DONE (Docker auto-start configured) - Phase 5: Ubuntu 24.04 ✅ DONE (new server running 24.04) - Phase 6-7: Monitoring ⏸️ Deferred
Why archived: Original plan was for incremental upgrades. We ended up combining several phases (Docker + nginx + Ubuntu 24.04) into a single migration to a new server, which was successful.
What we did instead: 1. Set up new Ubuntu 24.04 server with Docker from scratch 2. Migrated production to new server 3. Achieved same goals as planned but via different path
Historical value: Shows original thinking and planning process. May be useful reference for future upgrades (Python/Django versions, monitoring).
DEPLOYMENT.md¶
Status: ❌ Outdated
Superseded by: ../deployment/DOCKER_DEPLOYMENT.md
What it was: Deployment guide covering both local development and production deployment.
Why archived: Written for pipenv-based deployment. Production now uses Docker, making most of this guide obsolete.
Issues with this doc: - Mixed local development and production deployment - Assumed pipenv environment (no longer used in production) - No Docker-specific guidance - Deployment process has changed significantly
Current deployment guide: ../deployment/DOCKER_DEPLOYMENT.md covers:
- Three deployment scenarios (quick/full/rebuild)
- Docker-specific commands
- Disaster recovery procedure
- Production troubleshooting
Should I Use These Docs?¶
No, use the current documentation instead:
| Old Document | Use This Instead |
|---|---|
PRODUCTION_DOCKER_MIGRATION.md |
../deployment/DOCKER_DEPLOYMENT.md |
UBUNTU_24_FRESH_SETUP.md |
../deployment/DOCKER_DEPLOYMENT.md - Section 3 |
Uplink2.0_PLAN.md |
../deployment/Uplink2.0_UpgradeLogs.md (what actually happened) |
DEPLOYMENT.md |
../deployment/DOCKER_DEPLOYMENT.md |
When Are Archived Docs Useful?¶
These docs may be helpful for:
- Understanding historical context - Why decisions were made
- Rollback scenarios - If we need to revert to pipenv (unlikely)
- Learning from the migration - See what was planned vs. what actually happened
- Future upgrades - Reference for Python/Django version upgrades (Phase 2 of original plan)
Next Steps (Future Work)¶
From the original Uplink 2.0 plan, these items remain deferred but not forgotten:
- Python 3.12 upgrade - Currently on 3.9
- Django 5.x upgrade - Currently on 3.2 LTS
- Monitoring & observability - Structured logging, metrics, alerts
- CI/CD pipeline - Automated testing and deployment
See ../planning/ for future roadmap items.