A static web application
A static web application: a first setup, important settings, verification, and recovery considerations.
Working directory: ~/homelab/apps/custom-apps. Follow the common setup workflow first. This is a setup note based on the linked documentation, not a copy of my live configuration or a runtime verification of this full stack.
Start here
The downloadable practice lab is the runnable example for this entry. It serves one HTML file through Nginx and Traefik. Follow that guide from an empty practice directory; do not point its mounts at an existing website. This portfolio belongs to the same application category, but its live deployment is not included.
Settings and data
Edit apps/custom-apps/site/index.html in the practice project. Nginx sees that directory through a read-only bind mount. The application listens internally on 8080 and has no host publication; the gateway handles requests. There is no database or login in this sample.
Check it
Change the paragraph to your own test sentence, request http://lab.test:18080 with the documented curl mapping, and confirm the new text. Restore the original from your backup exercise. This verifies the file path, route, and recovery without collecting user data.
When something fails
A 404 from the gateway means you should check the requested host first. If the old page remains, inspect the source file and browser cache. A permission error calls for checking readable files and traversable directories, not making the entire project world-writable.
Run this only after the setup above, from its project directory:
sudo docker compose logs --tail 20 web gateway