Compute Caddy payload using Jinja2 with Ansible
Context As I may have mentioned in previous articles I run my services using Ansible to deal with the deployment and upgrade of different components. If we generalize the setup, it mostly consists of a reverse proxy (Caddy) listening on 443 and app stacks running under docker on their own network that connects to Caddy’s one. Something that looks like that: Issue My Ansible playbook is structured in a way where the reverse proxy is spawned first and then each app is deployed one by one, registering its own configuration against Caddy’s API in order to be served....
This Week's Articles (W17 2024)
Articles that caught my attention this week: https://read.highgrowthengineer.com/p/never-struggle-to-give-feedback-again https://newsletter.techworld-with-milan.com/p/how-to-fight-impostor-syndrome
This Week's Articles (W12 2024)
Articles that caught my attention this week: https://www.nngroup.com/articles/skeuomorphism https://www.sheshbabu.com/posts/thoughts-on-the-future-of-software-development
This Week's Articles (W9 2024)
Articles that caught my attention this week: https://newsletter.weskao.com/p/the-1-question-every-business-case https://newsletter.weskao.com/p/rigorous-thinking
This Week's Articles (W8 2024)
Articles that caught my attention this week: https://www.foxhound.systems/blog/technical-debt-is-not-real https://www.svix.com/blog/strong-typing-hill-to-die-on https://tidyfirst.substack.com/p/mastering-programming https://open-web-advocacy.org/blog/its-official-apple-kills-web-apps-in-the-eu/?utm_source=tldrwebdev
Could we stop prefixing booleans with the verb ?
A widespread convention when it comes to Boolean variables naming is to prefix them with a verb. Sometimes the explanation given for this practice is that it helps reading code, other times that this way we directly can spot that this is indeed a boolean. I would like to discuss those two assumptions. It helps reading code Maybe this is just me but I like when code reads like instructions. I agree that it can’t always be the case but I feel I should strive for it whenever I can....
1st Quarter plan 2024
Previous Quarter Plan A quarter plan (let’s start with a quick win!) ✅ A blog post on my first ever contribution to OpenStreetMap (don’t get your hopes high, it was a really really tiny thing) ❌ Continuing the CivicTech meetups by Les Bricodeurs ❌ Had to be put on hold for now, not that I don’t want to participate in anymore but those meetups have been paused so there’s that Refactoring of all the Ansible playbooks to deal with my server 🔁 This one has been started but is still an ongoing work....
4th Quarter plan 2023
As is not yet tradition, I will try to publish a quarterly plan of what I’d like to look at, try, and so on. This is mainly a personal thing to help keep track of what I was trying to achieve and what is my current advancement status. I’m not yet really sure of what the form of this report will be. I imagine some kind of retrospective on the previous one and some actions for the next quarter?...
How to backup your selfhosted server running under docker-compose
Need a backup strategy for your selfhosted docker-compose? Here is one!
Docker introduction for Les Bricodeurs
In order to shorten the famous list of things I forgot to post on time, here is the content of the workshop I gave for Les Bricodeurs “Docker pour les marins d’eau douce” on the 11th of March 2020 at the 42 Lyon Auvergne-Rhône-Alpes school. This workshop was the occasion to talk briefly about what Docker is and we then dove directly into using it and understanding it in order to deploy a Wordpress stack....