5.9 KiB
Proxmox Docker hosting
Configuration reviewed 10 November 2026. These instructions describe the checked-in configuration; a live deployment has not been verified. See verification.
Use a Linux guest with Docker Engine and the Docker Compose plugin installed. Copy this repository to the guest, or clone it after committing and pushing your changes. From the repository directory:
cp .env.example .env
# Edit .env: set BIND_ADDRESS to the portfolio guest's LAN IP.
docker compose up -d --build
docker compose ps
# Replace the example IP with the portfolio guest's LAN IP:
curl -f http://192.168.1.50:8080/healthz
Docker validates content, runs tests and builds inside a Node build stage. The build replaces its publication directory with exactly five validated static assets; only those assets enter the Nginx runtime image. The Docker context and Nginx public-file allowlists remain unchanged. No Node installation, database or persistent volume is required on the guest. Configure the guest and Docker to start on boot; the service uses restart: unless-stopped.
Network access
The default binding is 127.0.0.1:8080, accessible only on the Docker guest. A reverse proxy running directly on that guest can forward to it.
For access from your laptop or a reverse proxy on another machine, edit .env to use the guest's actual LAN IP:
BIND_ADDRESS=192.168.1.50
PORTFOLIO_PORT=8080
Run docker compose up -d again, then open http://192.168.1.50:8080 using your actual IP. Restrict port 8080 at the network/Proxmox firewall to the intended LAN or reverse proxy. Change PORTFOLIO_PORT if the port is already occupied.
Separate Nginx Proxy Manager box
Your topology is: Internet → Nginx Proxy Manager (HTTPS) → portfolio guest LAN IP:8080 (HTTP). The portfolio container needs no certificate or domain configuration.
In Nginx Proxy Manager, add a Proxy Host with these settings:
| Setting | Value |
|---|---|
| Domain Names | Your portfolio domain, such as portfolio.example.com |
| Scheme | http |
| Forward Hostname / IP | The portfolio guest's LAN IP, such as 192.168.1.50 |
| Forward Port | 8080, or your chosen PORTFOLIO_PORT |
| Access List | Publicly Accessible, for a public portfolio |
| Cache Assets | Off, so content edits revalidate immediately |
| Websockets Support | Off; this static site does not use WebSockets |
| SSL Certificate | Select an existing matching certificate or request one |
| Force SSL | On after the certificate is configured |
Leave Advanced configuration and Custom Locations empty. Serve the portfolio at the domain root. Hash routes, project links and both languages work without rewrite rules. Nginx Proxy Manager is designed to act as the gateway and manage SSL; see its official guide.
Use the portfolio guest's LAN address as the upstream, not localhost, the proxy box's IP or the Docker service name. Separate machines do not share the local Docker bridge network.
Point your domain DNS at the public address used by Nginx Proxy Manager. Your router's public ports 80/443 should reach the proxy box. Do not forward public port 8080 to the portfolio guest. At the Proxmox/network firewall, allow inbound TCP 8080 to the portfolio guest from the proxy box's LAN IP and deny other sources. Binding to a LAN IP alone does not impose this source restriction. These firewall/DNS settings must be applied in your infrastructure; this repository does not configure them.
From the proxy box, verify curl -f http://192.168.1.50:8080/healthz returns ok (substitute your IP). Then open the public HTTPS domain and test a project and language switch. If Nginx Proxy Manager returns 502, check the upstream IP, HTTP scheme, port, container status and firewall access from the proxy box.
Updates
Edit the JSON source files locally, run npm test and npm run build, then commit the JSON and generated content.js together and push. On the guest, keep local configuration in ignored .env and update a clean checkout with git pull --ff-only. If pulling fails because of local changes or divergent history, resolve that before rebuilding. Git also removes project files deleted upstream. Apply updates from the repository root with:
docker compose up -d --build
docker compose ps
curl -f http://127.0.0.1:8080/healthz
The health command above uses the default binding. If .env binds to the guest's LAN IP or changes the port, use that address and port instead. A push alone does not rebuild or deploy the site; there is no deployment automation in this repository.
Restarting alone does not import edited content; the files are baked into the image. Keep and back up the source checkout. Do not edit inside the container. To refresh base images, run docker compose build --pull, then docker compose up -d.
Operations and exposure
docker compose logs --tail=100 portfolio
docker compose ps
docker compose down
The container runs as the Nginx user with a read-only filesystem, dropped Linux capabilities and temporary memory-backed storage. The server exposes only the public website assets and /healthz; there is no admin or editing endpoint. Everything in the built content remains public. The development server is not used for hosting.
The health check expects /healthz to return ok. The restart policy handles process exits; an unhealthy status alone does not restart the container. Compose settings follow the Docker service reference.
During the initial documentation pass on 10 November 2026, the then-current six tests, static build and docker compose config --quiet passed. The suite has since expanded; see verification for subsequent results. The Docker engine was unavailable during that initial pass, so image build, runtime health, proxy access and Proxmox deployment remain unverified. Configuration validation alone does not prove that the container can start.