Home About Experience Projects 3D & Art
CV
Contact

Self-hosting & remote access

Debian/Apache architecture to expose personal services cleanly without directly opening the internal network.

Private self-hosted documentation portal dashboard with knowledge graph, folders and server context.

Genesis — self-hosted project-memory documentation portal

Genesis is an internal self-hosted documentation portal, based on MkDocs Material and Apache2, designed to become the official memory of BÊTA Studio.

  • Context : Transform a simple file space into a governed project-memory system: decisions, reports, mission orders, known issues and lessons learned.
  • Stack : Dedicated Linux VM, Apache2, MkDocs Material, Markdown, local genesis.beta domain, LAN/VPN-only access and build scripts.
  • Architecture : Clear separation between beta-knowledge as the editable source, portal-engine as the MkDocs/build layer, and published as the Apache-served static output.
  • Governance : Reusable document model with status, owner, confidence level, source, permanent ID, tags and linked documents.
  • Result : A traceable and maintainable knowledge base built for audits, long-term maintenance and controlled project evolution.
Debian server and web hosting visual.

Cleanly exposed Debian server

Controlled Linux base, limited services and HTTPS access.

  • Context : Host a portfolio and personal services without depending on an external platform.
  • Stack : Debian, Apache, PHP-FPM, Let’s Encrypt, UFW, fail2ban.
  • Actions : Virtual hosts, Apache/PHP hardening, TLS renewal, logs, webroot permissions and private data kept outside direct exposure.
  • Result : HTTPS website, reduced attack surface and reproducible maintenance.
Remote access, monitoring and infrastructure visual.

Guacamole & remote access

Browser-based remote access without directly exposing the internal machine.

  • Context : Access a remote environment from different terminals.
  • Stack : Apache reverse proxy, Guacamole, Basic Auth, WebSocket proxy, fail2ban rate limiting.
  • Actions : HTTPS proxy to the internal service, upstream authentication and login-failure monitoring.
  • Result : Three access layers: admin portal, Guacamole, then remote session.

VPN & internal network

Private access preserved for flows that should not be public.

  • Stack : WireGuard/VPN, NAT, port rules, logical segmentation through reserved local IPs.
  • Approach : Manual LAN IP assignment, reduced exposure, server-side and firewall logging.
  • Result : Clear separation between public HTTPS services and private administration.

Operations & hygiene

A personal project handled like a small production infrastructure.

  • Backups : Archives before changes, private data separated from the webroot.
  • Monitoring : Health checks, Apache/fail2ban logs and certificate control.
  • Documentation : Configuration kept understandable and reproducible independently.