Status: Base Camp Completed. Infrastructure Live. ๐ ๏ธ
This repository is my professional engineering workspace. It is built around a "Project Factory" philosophyโusing a modular, Docker-first architecture to rapidly scaffold, build, and deploy full-stack applications.
Instead of building monolithic apps, I use a decoupled system where the "Engine" (Backend) and the "Shell" (Frontend) are interchangeable parts.
- The Engine (Backend): : A shared Django 5.x REST Framework template with PostgreSQL, JWT Auth, and Swagger/OpenAPI documentation.
- The Shells (Frontends):
- Base: Standard clean-slate implementation for generic features.
- Minimalist: Focused on raw logic, speed, and clean typography.
- Dashboard: Tailored for data-rich administrative systems and analytics.
- Terminal: A retro-CLI aesthetic for system-level and security challenges.
- The Bridge: A centralized Axios
apiClientwith intelligent interceptors for dual-token management (User & Admin).
| Layer | Technology | Engineering Standard |
|---|---|---|
| Frontend | Vue 3 + Vite | Pinia state management, individual key token persistence. |
| Backend | Django 5.x | Custom User models, DRF Serializers, SimpleJWT. |
| Database | PostgreSQL | Relational integrity and Dockerized persistence. |
| Management | Port Mapper | Automated unique host-port allocation via port_registry.txt. |
| DevOps | Docker | Multi-container orchestration automated scaffolding with init-challenge.sh. |
Use the automation script to spawn a new environment:
# Usage: ./init-challenge.sh [Season] [Week] [Name]
./init-challenge.sh S1 Week-01 my-task-appNavigate to the created folder and start the stack:
cd ../S1/Week-01/my-task-app
docker compose up --build -dYour specific ports are stored in Base Camp/port_registry.txt. Standard initial offsets:
- Frontend UI:
http://localhost:5001 - API Root:
http://localhost:8001/api/ - Intractive Docs:
http://localhost:8001/api/docs/
To save system RAM and manage container lifecycles, use the Janitor script located in the Base Camp directory.
./janitor.shAvailable Actions:
- 1 START: Wake up a specific project by its port.
- 2 STOP: Hibernate a project to release CPU/RAM.
- 3 RESTART: Refresh a project stack.
- 4 STOP ALL: Emergency cleanup of all running containers.
| Period | Season | Focus | Standard |
|---|---|---|---|
| Jan | Base Camp | Infrastructure, Boilerplates, & Janitor Scripts | โ COMPLETED |
| Feb - Apr | S1: Mastery | Full-Stack Django & Vue 3 Challenges | ๐ก UPCOMING |
| May - Jul | S2: Expansion | Systems Programming (Rust/Go) & Microservices | โช PLANNED |
| Aug - Oct | S3: Intelligence | AI Integration & Data Engineering | โช PLANNED |
| Nov - Dec | S4: Scale | Cloud-Native Deployment & K8s | โช PLANNED |
- Live Observability: Heartbeat monitors in every shell to track API health.
- Clean Auth Flow: Automated silent refreshes and request-level token injection.
- Container Isolation: Zero dependency conflicts by running all shells in Alpine-based Node containers.