CLOUD / PROJECT NOTES
Azure cloud portfolio
A hands-on portfolio environment combining an Ubuntu virtual machine, containerized services, domain routing, and HTTPS.
Project context
The repository documents an Azure Ubuntu VM and a Docker-based portfolio. Its saved Caddy configuration routes the frontend and backend separately.
Engineering approach
Separate application delivery from shared infrastructure. Validate a release before promoting it, and keep a previous version available for rollback.
Explore the implementation
The public repository contains the portfolio frontend, a saved reverse proxy configuration, and delivery workflows. It does not contain the complete server-side application.
View repository ↗Interactive architecture
Expand each layer to follow a request through the documented design.
1. DNS & HTTPS
DNS selects the hosting destination. The certificate must cover the exact hostname requested by the browser.
2. Reverse proxy
In the Azure design, Caddy terminates HTTPS and forwards application requests. GitHub Pages serves static files separately and cannot execute the Flask API.
3. Application & data
The frontend presents projects. A backend must validate requests and persist data before reporting success. Database access belongs on a private network.