Installed and hardened a bare-metal Proxmox hypervisor (dual-bridge network isolation between public SaaS and admin VPN, encrypted ZFS mirror, CrowdSec, remote PBS backups over VPN)
Automated multi-tenant provisioning with Bash scripts, deploying lightweight Alpine Linux LXC containers hosting Docker Compose stacks (cumulatively sized for ~100 customer instances)
Built a 5-stage GitLab CI/CD pipeline to automate the development cycle (testing, Docker image packaging, ADTi private registry push, dev staging, and E2E validation)
Developed an industrial IoT data pipeline (ESP32, MQTT/Mosquitto, Node-RED) with state management (observation window, cooldown) to auto-trigger CMMS work orders from configurable thresholds (e.g. alerting assigned teams on unusual sensor temperatures)
Refactored .NET authorization architecture by migrating permission checks to API controllers across 500+ endpoints, verified through non-regression test suites
In collaboration with my friend Jonas Facon (former colleague at ADTi + classmate at BUT), we developed a common Proxmox base that we then forked for our personal needs - About
The main goal of this project is to learn how to manage a Proxmox / Kubernetes platform and, if possible, push it to the limits of automation and reliability.
Secrets management note (SOPS / age)After first using OpenBao (to learn Vault usage), secrets are now managed on Git using SOPS / age and loaded through Ansible playbooks. For ArgoCD, secrets are decrypted by the SOPS Kubernetes Operator, itself deployed as an ArgoCD app.
Development of a LaTeX web editor where users can write live on a document, compile to PDF, and save their projects with their account. Writing all my school reports in LaTeX, it helped in the writing of live-group reports.
I have other school group projects that you can find on GitHub: Matrix Server (automated multi-VM deployment, BATS testing, Bash orchestration), EcoDrop REST API (Java EE, PostgreSQL, GitLab CI/CD with 70 Bruno integration tests), and Modulab (procedural maze game in Java).
…And their organization
All of my personal projects are tracked by 3-month long plannings on kanban.blavogiez.fr (using Kanboard), since May 2026. In this context, it mostly helps on prioritization. You can find the current planning here and reviews on my GitHub, where I note areas of improvement over time.
As I usually spend between one and five hours a week on personal projects, expect roughly 36 hours for each planning, and 8 to 12 tasks. A typical task consists of 25% planning, 50% implementation and 25% quality reviewing, and is formulated through a Problem -> Solution idea.
Skills
Most of these are used in my day-to-day personal project administration, which consists of Kubernetes workloads running in Proxmox.
Vault / OpenBaoWireguard VPNCloudflare tunnelsCaddyProxmox firewall / ufwSOPS / age
Observability
PrometheusLokiGrafanaGrafana AlloyGrafana k6 (load testing)Exporters development (TS)
Development & Scripting
PythonTypeScript (GHA)JavaJava EE / TomcatNode.jsPostgreSQLREST API
Soft skills
English C1 (TOEIC 960)Kanban organizationAgile methodologyCollaborative teamwork
Principles I follow
Improving my work methods through feedback and/or self-questioning
End users know their needs best. In school projects, I tried to align closely with teachers’ expectations, and during my internship, I made sure to clarify clients’ requirements before planning any solution.
Code reusability and templating (in my case, usually with Jinja2 or Helm)
Building reusable custom CI/CD pipelines across projects to address common needs
Single source of truth, both for infra and dev (it can be Git for deployments, Makefiles for commands…)