$ project self-hosting-this-site

Self-hosting the website that documents the project

Project 01Status: activeCurrent topic: HTTPS / TLS

The public lab endpoint now runs on infrastructure I build and operate myself. The current stage is adding HTTPS while keeping the exposure deliberately minimal.

A provider-hosted copy remains available as a fallback, while lab.siddle.nl is now served from my own infrastructure over public HTTP.

The migration is being treated as a system administration project rather than simply a web-design task. The physical host, KVM/libvirt layer, bridged VM networking, nginx web server, public DNS and IPv4 port forwarding are now functioning; HTTPS is next.

The important part is not only whether the website works. The objective is to understand and document the layers underneath it.

$

architecture_chain

physical hostLinux OSvirtualizationVMnetworkingweb serverHTTPSfirewallmonitoringbackupspublic service
$

current_status

$

phases

  1. Publish portfolio at current provider
  2. Prepare Ubuntu host
  3. Learn KVM / libvirt
  4. Build server VM
  5. Configure bridged VM networking
  6. Deploy nginx web server
  7. Publish DNS and minimal HTTP exposure
  8. HTTPS / TLS
  9. Firewall hardening and exposure review
  10. Monitoring and backups
  11. Complete production migration
  12. Document final architecture
$

public_documentation_rule

Reasoning and architecture are public; unnecessary attack surface is not.
Passwords, tokens, private keys, exact credentials, router exports, client information and other sensitive material are excluded. Internal network details are generalized where exact values add no learning value.