<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Antoine Boucher</title><link>https://antoineboucher.info/CV/blog/tags/devops/</link><description>Recent content in DevOps on Antoine Boucher</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://antoineboucher.info/CV/blog/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>My reverse proxy: separating provisioning, configuration and health checks</title><link>https://antoineboucher.info/CV/blog/posts/reverse-proxy-infrastructure/</link><pubDate>Thu, 22 Oct 2026 00:00:00 -0400</pubDate><guid>https://antoineboucher.info/CV/blog/posts/reverse-proxy-infrastructure/</guid><description>&lt;p&gt;My reverse-proxy project uses Caddy on a DigitalOcean VPS, with Cloudflare DNS. Terraform creates the infrastructure, Ansible configures it, and separate checks examine the resulting service.&lt;/p&gt;
&lt;p&gt;This article describes the repository as reviewed on October 22, 2026. The source is private, so the diagram is deliberately simplified and contains no real domains, addresses or credentials. I reviewed the code without running a deployment.&lt;/p&gt;</description></item></channel></rss>