heleosv2 multi-tenant hosting platform (infra + CLI)
Idempotent host configuration targeting Ubuntu 24.04 with ZFS on a dedicated second disk. Role-based platform-infra/ansible: - base: apt packages, timezone, unattended security upgrades. - zfs: install ZFS, create pool on a dedicated disk (guarded against wiping a non-empty disk), create platform datasets + customers parent per docs/03; docker dataset mounted at /var/lib/docker. - docker: Docker Engine + Compose plugin, daemon.json written before first start so the native zfs storage driver initializes on the ZFS data-root; per-site network address pool preconfigured. - firewall: nftables inbound default-deny in a dedicated table that never flushes Docker's rules; container outbound SMTP blocked via a DOCKER-USER jump applied by a systemd oneshot. - ssh_hardening: key-first SSH with an anti-lockout assertion, config validation gate, and the sftponly group for Phase 4 SFTP accounts. Includes ansible.cfg, requirements.yml, inventory example, group_vars with safety notes, and a run guide. Real inventory (hosts.yml) is git-ignored. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| control-panel | ||
| deployments | ||
| docs | ||
| platform-infra | ||
| site-templates | ||
| .gitattributes | ||
| .gitignore | ||
| README.md | ||
heleosv2 — Multi-Tenant Web Hosting Platform
A rebuild of a small web-hosting business on modern, isolation-first infrastructure: container-per-customer + ZFS-dataset-per-customer, with repeatable CLI-driven provisioning and clean per-customer backup/restore.
Core philosophy — the customer is the boundary. Isolation (containers), backup (ZFS), and restore all line up on the same boundary, so a compromised or broken site is contained and restorable without touching neighbours.
Status
Phase 0 — writing the design documents before any platform code. See
docs/00-roadmap.md.
Repository layout
This monorepo groups four logical areas whose contents have different
lifecycles (see docs/07-repo-layout-gitops.md):
| Path | Purpose |
|---|---|
docs/ |
Architecture, ADRs, runbooks, conventions. |
platform-infra/ |
Ansible + base compose for host, Traefik, MariaDB, Forgejo, monitoring. |
site-templates/ |
Dockerfiles for standard images + compose templates per site profile. |
deployments/ |
Rendered per-customer configs (GitOps state). No plaintext secrets. |
control-panel/ |
Provisioning CLI now; customer-facing panel later. |
Key decisions
- Single bare-metal host, Docker Compose per customer, no orchestrator.
- Shared MariaDB (per-site DB + least-privilege user).
- Decoupled backups: web files via ZFS snapshot/
send; DB via automysqlbackup + rsync; logs via Loki. - Lightweight DevOps: Forgejo + built-in registry + Trivy.
- CLI-first provisioning; web panel deferred until the platform is proven.
The full approved architecture plan lives at
docs/architecture-plan.md.