Building Reliable Infrastructure with Open Source and DevOps Practices

Self-hosted infrastructure, automated deployments and reproducible platforms built with Docker, Ansible and modern Linux tooling.

Client Logo 1

This website is both a technical portfolio and a living infrastructure laboratory where I design, automate and operate self-hosted platforms.

Sébastien Clem

Founder of lavallee.tech

Why I Built This Infrastructure

From Teaching to Infrastructure Engineering

For several years I have been teaching computer science courses in a local association.
My classes rely heavily on practical exercises, which means I constantly deploy virtual machines to demonstrate real-world scenarios.

This naturally led me into the world of self-hosting and digital sovereignty. I am also a member of ARN, a community-based ISP in Alsace, which further strengthened my commitment to open-source technologies and decentralized infrastructure.

You could say I have become a strong advocate for open-source and self-hosted services.

The Initial Problem

Over time, my infrastructure grew organically.

I had:

  • many virtual machines

  • multiple web services

  • different hosting experiments

  • various configurations spread across servers

While this setup worked, it lacked structure and reproducibility. At the same time, my students increasingly asked the same question:

“How do you deploy web applications with Docker in a clean and reproducible way?”

That question triggered the idea behind this project.

Turning a Personal Lab into a DevOps Platform

I decided to reorganize my infrastructure and document it properly. What started as a personal clean-up quickly evolved into something bigger:

A reproducible, automated, and production-ready web hosting platform.

  • automate deployments

  • structure the infrastructure

  • version everything

  • make the system reproducible

  • document the entire architecture

The result is a living Proof-of-Concept for self-hosting infrastructure. This very website is hosted on a VM that is part of that platform.

Infrastructure as Code Approach

The platform allows me to deploy, maintain, and evolve web applications using modern DevOps practices:

  • Infrastructure automation

  • Reproducible deployments

  • Version-controlled configuration

  • Isolated application environments

Applications currently hosted include:

  • WordPress websites

  • Nextcloud services

  • Radiocast streaming

  • various experimental web services

Technical Architecture

Network Flow

  • 1

    Public traffic arrives on a VPS with a public IP address

  • 2

    Traffic is forwarded through a WireGuard tunnel

  • 3

    A dedicated Caddy reverse proxy VM manages TLS certificates and routing

  • 4

    Requests are forwarded to isolated Docker stacks hosting the applications

This architecture provides:

  • secure tunneling

  • centralized TLS management

  • application isolation

  • flexible scaling

Project Evolution

The project is currently structured into three levels of complexity.

Level 1 — Basic Infrastructure

A single VM running a reverse proxy.

  • infrastructure layout

  • Ansible project organization

  • basic service deployment

Level 2 — Reverse Proxy Architecture

A dedicated Caddy reverse proxy VM handles:

  • automatic TLS certificates

  • domain routing

  • traffic forwarding to the application VMs

This introduces a more realistic production architecture.

Level 3 — Reliability Layer

The third level adds operational capabilities:

  • automated backups

  • monitoring and observability

  • infrastructure resilience

Building and Sharing Open Infrastructure

This infrastructure is not just theoretical. It is part of a broader commitment to:

  • test deployment strategies

  • experiment with infrastructure design

  • document real-world DevOps practices

The platform is documented to help others understand how modern DevOps practices can be applied to self-hosted systems. Every improvement is versioned, turning the project into both a technical lab and a reproducible infrastructure blueprint.

Interested in the technical details?

Explore the architecture, documentation and source code.