triptico.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I updated my tiny FreeBSD box (powered by FreeBSD 15.1-RELEASE) and its three jails during my breakfast. There was a lot of security patches but it was fast to install (~10 minutes to fetch, to install and to restart everything).
#FreeBSD #bastilleBSD
The November 17th, 2026 Jail/Zones Production User Call is up:
We discussed a kernel work queues update, the Casa system deployment and management tool, MediaTek SoC's, experiences as a new #FreeBSD contributor, and more!
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
This content is not AI generated
Today is the perfect day to read this, you will know why after you start to.
Beyond Linux: A Journey Through the Open Source Ecosystem
A journey beyond Linux, exploring BSD, illumos, and other alternative operating systems, and reflecting on open source as a philosophy of freedom, collaboration, and sharing knowledge.
https://it-notes.dragas.net/2026/11/17/beyond-linux-a-journey-through-the-open-source-ecosystem/
#ITNotes #NoteHUB #FreeBSD #illumos #Linux #NetBSD #omnios #OpenBSD #OpenIndiana #OwnYourData #SmartOS #Tribblix
https://it-notes.dragas.net/2026/11/17/beyond-linux-a-journey-through-the-open-source-ecosystem/
#ITNotes #NoteHUB #FreeBSD #illumos #Linux #NetBSD #omnios #OpenBSD #OpenIndiana #OwnYourData #SmartOS #Tribblix
IT Notes - https://it-notes.dragas.net » 🤖 🌐
@itnotes@snac.it-notes.dragas.net
https://it-notes.dragas.net/2026/11/17/beyond-linux-a-journey-through-the-open-source-ecosystem/
#ITNotes #NoteHUB #freebsd #illumos #linux #netbsd #omnios #openbsd #openindiana #ownyourdata #smartos #tribblix
How can companies reduce the challenges of maintaining a customized FreeBSD codebase while contributing improvements back to the Project?
At the November 2026 FreeBSD Vendor Summit, Amy Vargas from NetApp shared the company's journey toward upstream contributions in her presentation, “NetApp's Journey of Upstreaming to FreeBSD.”
Watch the full presentation: https://youtu.be/HrNrkvR8KaA
I just received a rather interesting sales email.
Here's the full message, translated from Italian:
Good morning (it's 19:16 here!!!) Stefano,
I read about your migration from Proxmox to FreeBSD jails to reduce operational times.
My team and I build automations to produce, for example, reports on completed work without having to manually copy information. For Penguin Engineering, we analyzed their workflows and identified activities that could be automated.
Would you be available for a short call to explore whether automating report preparation could save your team some time too?
Hello AI
Giammaria
So, let me get this straight.
You read about my migration from Proxmox to FreeBSD jails. A technical decision involving infrastructure, virtualization, system architecture, and operational efficiency. And your conclusion was that I might need help... automating reports Reports?
I talk about FreeBSD jails, you talk about copying information into reports. That's quite an impressive logical leap. Even for an AI.
I'm almost tempted to reply and ask whether they could automate the process of sending irrelevant sales emails based on keywords extracted from blog posts.
Oh, wait.
I think they've already solved that problem. Anyway, I do have an automation solution for emails like this.
It's called /dev/null. It's infinite.
Free, reliable, incredibly fast, and available on virtually every Unix system.
No subscription or "AI" required.
Manpage Monday: bastille sysrc
Safely edit rc.conf inside a jail from the host.
Enable nginx in a jail
> bastille sysrc myjail nginx_enable=YES
Disable caddy
> bastille sysrc myjail caddy_enable=NO
Add -a and it'll start a stopped jail, apply the change, then carry on.
See `man bastille-sysrc` for more details.
Getting the room ready before my talk at Linux Day 2026 in Modena, on 24 October: "Beyond Linux: A Journey Through the Open Source Ecosystem."
Tomorrow, on IT Notes!
#ITNotes #StayTuned #OwnYourData #AvoidMonoculture #FreeBSD #NetBSD #OpenBSD #illumos #RunBSD #Linux #OpenSource #FreeSoftware #BeFree
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟭𝟭/𝟭𝟲 (Valuable News - 2026/11/16) available.
https://vermaden.wordpress.com/2026/11/16/valuable-news-2026-11-16/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Geophysicist here. I've spent 25+ years analyzing large-scale geophysical data, which is data science by another name. Now I want to own my working environment, so I'm taking a detour through FreeBSD. 🐡
Debian is my daily driver. The lab: a 2011 Sony Vaio netbook (AMD E-350, 6 GB RAM, 120 GB SSD) getting FreeBSD 15.1 + MATE.
Goal: get my geoscience stack (Python, GMT, QGIS) running on it.
New to FreeBSD, so tips are welcome!
RE: https://mastodon.bsd.cafe/@vermaden/117589595254181009
Added 𝗨𝗣𝗗𝗔𝗧𝗘 𝟭 [UPDATE 1] to 𝗡𝗲𝘄 𝗙𝗿𝗲𝗲𝗕𝗦𝗗 𝗽𝗸𝗴𝗯𝗮𝘀𝗲(𝟴) 𝗧𝗼𝗼𝗹 [New FreeBSD pkgbase(8) Tool] article.
https://vermaden.wordpress.com/2026/11/10/freebsd-pkgbase-update-tool/#UPDATE1
#verblog #freebsd #pkgbase #pkg #update #upgrade #tool
Has anyone written documentation or a tutorial on how to write a plugin for the #FreeBSD package manager?
EDIT: Please note, this post hasn't been update for a long time and still considers Dovecot 2.3.x - but the underlying ideas are still current.
Quite relevant, today:
Make your own E-Mail server - Part 1 - FreeBSD, OpenSMTPD, Rspamd and Dovecot included
FreeBSD's latest Status report offers interesting insights into what the community thinks about using AI. Most importantly, the vast majority favor clear policies and mandatory disclosure rules. Many Open Source projects can learn from the results.
#opensource #freebsd #AI
https://www.freebsd.org/status/report-2026-07-2026-09/
The recording of the November 12th, 2026 #bhyve Production User Call is up:
We discussed several #FreeBSD fixes that help #Sylve, the vmm Test Harness, VM checkpoints, Sylve roles and delegation, Podman advantages, the Sylve GUI options, higher-performance storage for CI VMs, and more!
"Don't forget to slam those Bike and Describe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
This content is not AI generated
I've always appreciated the simplicity of the BSDs. Power, yes, but without unnecessary complexity.
BastilleBSD and vm-bhyve have been my trusted companions for many years. But whenever I used Linux, I missed them.
That's why, years ago, I started putting together a collection of shell scripts (and some Python, although to a much lesser extent) to create something somewhere in between.
A bit of Bastille, a bit of vm-bhyve, a bit of Proxmox: unprivileged Linux system containers and virtual machines, managed from the command line.
Live backups. And live restore: bringing a workload back online before all its data has finished copying from the backup. Multiple storage backends. Encryption at the storage or individual workload level. Different networks. Isolation of each workload (a bit like illumos zones), with additional layers of protection.
Each container has its own UID/GID mapping. VMs run under separate unprivileged identities, with namespaces, seccomp and resource limits adding further layers of protection.
Pull-based backups from external hosts, with different levels and types of encryption. With raw encrypted ZFS replication, the backup server doesn’t even need the decryption keys. Backups are pulled over SSH by an external server. The workload host holds no credentials to log in to that server.
It also runs on a 1 GB Orange Pi PC 2, where I’ve tested both containers and native ARM64 KVM guests. And on a Orange PI One, armv7 and 512MB, it can run some lxc containers without problems, from the SD, using f2fs.
Simple disaster recovery. Because after those 142 servers went up in flames in Strasbourg, disaster recovery became something I care a lot about.
Currently supported and tested on Alpine Linux, Debian 13 and Armbian. On Debian, LXC containers also run under enforcing AppArmor profiles, adding another layer of protection.
Few commands. Lots of power. And it's called "Jail It!"
I'm not going to release it, at least not for now. I need to focus on my other projects, and Jail It! still needs some cleaning up.
But it works. And it does its job very well.
For containers, there's absolutely nothing running in the background. For VMs, just a small Python helper. No continuously running services. You connect via SSH, run your commands, and that's it.
Still, for anyone curious enough to have a look, I've put together a short demo on Asciinema:
https://asciinema.org/a/BbwGs99U9UJDLAzZ
Well, "short" might be a bit of an exaggeration. It's quite long, but I think it's worth watching all the way to the end.
#Linux #LXC #KVM #FreeBSD #Virtualization #OwnYourData #BSD #SelfHosting #Homelab #SysAdmin #DisasterRecovery
I really, really reeaaallly want to see #Sylve becoming a FreeBSD based replacement or alternative to #Linux solutions like #XCPng (#Xen) or #Proxmox (#KVM).
Also interesting for my own @BoxyBSD@bsd.cafe project utilizing this feature. So, I've been working at this for some time now.
First working draft moving a VM which has its storage on a NFS server (ZFS based send/rec. as local storage to follow), including multi CPU support. But there's a catch - I'm not sure if I want to publish this later under MIT, rather than GPLv3 or AGPLv3, so this could be a problem for upstreaming.
Has anyone experimented with using a Linux jail for gaming? Would it work with Wine?
I have a game which has a launcher that would only run on Linux but it launches a game with Wine. I wonder if there's a way to run Wine on FreeBSD but keeps the launcher using linuxulator. 🤔
RE: https://masto.ai/@phoronix/117597611145334204
I think these polls reflect the leaning already know for FreeBSD to heavy regulate LLMs use than jump in without regards like the Linux Kernel and other related projects. Thought probably I believe, if they will do a final guideline, they are going to relegate AI usage for tasks like documentation (and the pools reflects that), and get al least a strict guideline about the code that isn't going to fall far to the other BSD projects, perhaps a bit more permissive.
FreeBSD Working To Establish An AI Policy After Polling Developers
The FreeBSD Project published its Q3'2026 status report on Tuesday that outlines a number of development initiatives to ongoing work around an AI policy for this BSD operating system...
https://www.phoronix.com/news/FreeBSD-Q3-2026-Report
FreeBSD Developer AI survey
https://www.freebsd.org/status/report-2026-07-2026-09/#_freebsd_core_team
BSD folks: Is there a native #FreeBSD, #OpenBSD, or #NetBSD tool for managing system-wide trust-anchors? Debian has something like
$ sudo dpkg-reconfigure ca-certificates
which gives an interactive TUI allowing me to specify which CAs I do/don't trust, and they get picked up system-wide.
Ideally this would persist past most package/system upgrades too so I don't have to (re)do it every time ca-certificates gets updated from repos.
Was chatting with Hayzam yesterday about Sylve and integrating daemonless (https://daemonless.io) directly into it. Seeing it turn painful setups like Grafana and VictoriaMetrics into 10-second deployments is exactly why we're doing this.
It hit on a familiar feeling: remember when getting a new phone was exciting? Setting up every app, tweaking configs, logging into everything. Nowadays, it's just a chore you want over with. Babysitting packages and doing low-level sysadmin work on standalone jails feels the exact same way.
Wrote down some thoughts on moving past that friction: https://ahze.net/posts/the-new-phone-feeling/
#FreeBSD #daemonless #Sylve #containers #SelfHosted #SysAdmin
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟭𝟭/𝟬𝟵 (Valuable News - 2026/11/09) available.
https://vermaden.wordpress.com/2026/11/09/valuable-news-2026-11-09/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
The Sovereign Tech Agency is seeking input from the open source community to help shape the EU Sovereign Tech Fund pilot, an initiative focused on supporting critical open source technologies that Europe's digital infrastructure depends on.
We encourage FreeBSD users and contributors, particularly those in Europe, to participate and share their perspectives on the open source infrastructure they rely on.
Take the survey: https://survey.sovereign.tech/eustf
Manpage Monday: bastille config
Get, set, add or remove jail properties — no manual jail.conf edits.
Allow mlock inside a jail
> bastille config myjail set allow.mlock 1
Set a start priority
> bastille config myjail set priority 10
Read a value back
> bastille config myjail get boot
See `man bastille-config` for more details.
Typical example of the sort of myopia that is usually part of using the generic "BSD" moniker:
https://docs.ansible.com/projects/ansible/latest/os_guide/intro_bsd.html says "how to use this on BSD"; it has examples for both BSDs -- #FreeBSD and #OpenBSD and does not mention #NetBSD a single time!
I keep seeing this. Why?
Haven't tried OCI containers on FreeBSD yet? Try fjord, a web UI app store for FreeBSD containers.
6-minute walkthrough: https://youtu.be/8S3hEVyCUzc
Not your thing? Sylve (nightly) and FreeCORE run daemonless images too, and so does plain Podman or AppJail.
When I'm asked why OpenBSD is good and that I want to reply honestly, I have no argument.
From a technical point of view, I can't tell any strong benefits using OpenBSD, NetBSD or FreeBSD over Linux, although this doesn't mean they are bad.
It would be easy for me to be "cargo-culting" facts, being a "fanboy" or enumerating features that are exclusive to one (and they are rare, except if you are looking for the very very same feature!).
The truth is that what one OS will do better than an other, it will also do worse in another area.
It's important that we keep the BSD systems as relevant Linux alternatives: for software diversity, innovation and freedom of choice.
This week, I had to do some work with Linux, so I found myself working with Alpine Linux again. And, of course, one of the worst and most absurd security vulnerabilities in recent times popped up. 😆
Fortunately, none of my setups met the conditions required for exploitation.
That said, I've been running some interesting experiments on a Raspberry Pi 4, the same one that has been running FreeBSD for quite some years, hosting a Time Machine service in a jail and handling backups from other servers.
Long story short, I installed Alpine Linux on the Raspberry Pi and moved FreeBSD into a KVM virtual machine, with the disks passed through directly to it.
The result? The VM runs beautifully with 3 GB of RAM (possibly even 2 GB), and I still have the rest of the Raspberry Pi available to run OpenBSD, NetBSD, and other systems I need for different setups.
It's a sad that bhyve doesn't (yet) support virtualization on that device. Or at least, that was still the case the last time I checked.
Please don't scroll past. This is important.
(edit: Note that the FreeBSD subreddit is in no way affiliated with the official FreeBSD project.)
I am being pressured by FreeBSD's reddit moderation team to censor the Omarchy #content_review or to remove it completely. They have began a harrasment campaign with the goal of removing me from this world.
the review: https://merveilles.town/@prahou/117501303459299869
The issue at hand is that a picture of a partial swastika appears in close proximity to the word FreeBSD, this they perceive as an attack on the FreeBSD project - if you've seen a newspaper before, you might understand the principle of two separate unrelated articles appearing next to each other. You might also understand that I am reporting on common associations with the Topic of the review. These are not my inventions, and I am not calling anyone anything. I am reporting on the news. Nevertheless, as much as I am a journalist, I am an artistè, and if my audience sees in my work something I didn't put there, I am not going to take that experience away from them. This probably says more about them than it does about me.
While I am a man of principle, there is one thing I like more - money.
I will delete it for $2,000. For $5,000 I will apologize. For $10,000 I will use daemonarchy exclusively for 6 months on all my computers. For $25,000 I will not do anything. For $75,000 I will not post anything for a month.
https://liberapay.com/analognowhere
https://ko-fi.com/analognowhere
To everyone who likes my work, this message is for you (from said freebsd moderator) [cw ableist slur]: https://beige.party/@fuzzy/117510032933612034
To everyone else who feels personally attacked by my art: send money, you can end this here and now.
Thank you for your attention.
pls boost
#runbsd #omarchy #fediverse #fediart #unix_surrealism #swastika #freebsd #news
BOMBSHELL TAPE STUNS THE PRESIDENCY
since this is being linked: here's the truth: https://merveilles.town/@prahou/117511205187027547
#content_review #omarchy #linux #runbsd #freebsd #comic #art #fediverse #programming #ai #neverslop
some days I wish upgrading #FreeBSD was as mindless as upgrading my #OpenBSD machines.
On OpenBSD, it's generally `sysupgrade`, let it do its thing, rebooting itself a couple times (entering my FDE passwords as necessary), and then a `pkg_add -u` to upgrade my packages. Sometimes a `sysmerge` if it can't do it automatically. But very much two (or three) idiot-proof commands with very little demand on this idiot's brain to recall where I am in the process.
While I like the automatic ZFS boot-environment snapshotting, FreeBSD requires me to know the next version-number I want to upgrade to (can't determine it or prompt me for viable options?), transcribe it as part of the upgrade command, then manually running `freebsd-update install` multiple times, rebooting manually multiple times between each, then `pkg update` and a `pkg upgrade` to update userspace. I'm sitting at a login…is this the first, second, or third reboot? I don't know, it was taking a while and I ended up wandering off to do something else.
This post brought to you by this morning's 14.3→14.4 FreeBSD upgrade 😆
EDIT: the recording is available here: https://exquisite.tube/w/nQbc54t4G7YGaqiryZ7mg1
On 10 March 2021, I had only just fallen asleep when my phone started buzzing. Then another notification, and another. In a matter of minutes, 142 of my servers went up in the clouds. And not the cloud-computing kind.
Most of them were physically going up in a column of smoke in Strasbourg.
My wife looked at me and asked if I wanted a coffee. I nodded. It was going to be a very long day.
At EuroBSDCon 2026, I won't be giving a theoretical lecture on high availability. Instead, I’m going to tell the raw story of that night: the emergency recovery, the architectural choices that actually saved us, and the ones that crumbled under pressure (because we rarely talk about what fails).
Most of all, I’ll explain why that night changed my perspective, and why I’ve come to see BSD systems not just as operating systems, but as essential, practical tools for building simpler, more resilient infrastructure.
The official schedule is now live. If you want to hear a real-world post-mortem, join me on Saturday, 12 Sept at 11:15 (Room D.0.02).
EuroBSDCon Full schedule: https://events.eurobsdcon.org/2026/schedule/
See you there! ☕️
#FreeBSD #NetBSD #OpenBSD #DragonFlyBSD #RunBSD #EuroBSDCon #SysAdmin #SelfHosted #IT #EuroBSDCon2026 #BSDCon
Great news! My presentation for #EuroBSDCon has been accepted!
Expect a mix of disasters, horror stories, recoveries, BSDs, and one very, very long day.
Stay tuned!
#EuroBSDCon2026 #BSD #RunBSD #FreeBSD #NetBSD #OpenBSD #Linux
When I wrote about FediMeteo (https://it-notes.dragas.net/2025/02/26/fedimeteo-how-a-tiny-freebsd-vps-became-a-global-weather-service-for-thousands/) for the first time, I told the story from the beginning: the idea born almost by chance while checking the weather for a holiday, the memory of my grandfather, who for years had been my personal meteorologist, the decision to build something small and useful, and then the surprise of seeing people actually use it. What began as a personal experiment quickly became a small global service, still running with the same philosophy: FreeBSD, jails, simple scripts, snac, text, emoji, and a lot of small pieces doing their work quietly.
That article was mostly about the birth and growth of the project. This one is about one of the less romantic parts of the same story, although I have to admit that I find a certain beauty in it too: keeping the service light as it grows.
FediMeteo (https://fedimeteo.com) is still intentionally simple from the outside. A homepage, some numbers, a list of countries, and many ActivityPub accounts publishing weather forecasts. The posts are text and emoji. There is no JavaScript requirement to read the pages, no heavy frontend, no unnecessary media attached to every forecast, and no dynamic homepage recalculated at every visit just to show the same numbers. This is not accidental. It is the way I wanted the service to behave from the beginning.
But the more the service is used, the more the small details matter. A request that looks harmless when there are ten followers may become a repeated request when there are thousands of followers, remote instances, crawlers, previews, and other servers fetching the same public objects. In the Fediverse, the same small thing can be asked many times by many different places, each one with a perfectly legitimate reason. The backend doesn't care: it just needs to deal with the requests.
And in FediMeteo, the backend is snac (https://codeberg.org/grunfink/snac2).
I like snac very much precisely because it is small, clear, and efficient. It is not a giant application that tries to be everything. It does a focused job and does it well. But this also means that I want to respect its shape. I do not want to waste its threads on work that the reverse proxy can safely do. A snac thread serving the same public avatar again and again is not a tragedy, but it is still a waste. A snac thread answering the same public ActivityPub object several times in the same minute is doing real work, but often not necessary work.
This is the reason behind the HAProxy (https://www.haproxy.org) tuning I am currently using in front of FediMeteo.
It is not about making the configuration look clever. It is about keeping snac quiet.
This is especially important because snac uses a limited number of threads. I like that. Limits are healthy. They force us to understand what the service is doing, and they prevent a small program from pretending to be an infinite resource. But limits also make waste visible. If a few threads are busy serving files that could have been served from cache, those threads are not available for something more useful.
With FediMeteo the implementation is different because the reverse proxy is HAProxy, but the reasoning is the same. I have many small snac instances, each one in its own FreeBSD (Bastille (https://github.com/BastilleBSD/bastille)) jail, and one public entry point that has to route, terminate TLS, compress, cache, and generally remove as much repetitive work as possible from the backends.
This is, in a way, the natural continuation of the original FediMeteo design. In the first article I wrote that I wanted to manage everything according to the Unix philosophy: small pieces working together. This is another piece of that same puzzle. HAProxy does the edge work. snac does the ActivityPub work. Scripts generate forecasts. cron launches updates. ZFS gives me snapshots. FreeBSD jails keep countries separated. Nothing is particularly heroic by itself, but the whole system becomes pleasant because each part has a clear responsibility.
FediMeteo does not use media in its forecasts.
No images attached to the posts, no generated weather cards, no maps for each city, no decorative banners. The forecasts are text and emoji. This was a deliberate decision. Weather information does not become more useful just because it is put inside an image, and every media file used by the service would become something to store, serve, cache, federate, expire, back up, and occasionally debug.
Text and emoji are enough. They are accessible, light, readable in text browsers, friendly to timelines, and understandable even when someone does not know the local language perfectly. This was one of the original design principles of FediMeteo, and it also helps the infrastructure. Less media means less work, fewer cache entries, fewer repeated fetches, fewer surprises.
There is one exception: the avatar.
All FediMeteo accounts use the same avatar, and this is also intentional. I could have used a different avatar for each country, or for each city, or created something visually richer. It would have been nicer in some screenshots, perhaps. It would also have been operationally worse.
With one shared avatar, the reverse proxy has one very useful object to cache. It is public, identical for everyone, small, requested often, and therefore almost always hot in cache. HAProxy can serve it directly instead of asking each snac instance to return the same file. Since avatars are requested by remote instances, browsers, profile previews, and all sorts of federation-related fetches, this single decision removes a surprising amount of pointless backend traffic.
So the avatar is not only a visual identity. It is part of the architecture.
This is the kind of optimization I like most, because it starts before the software. It starts with deciding not to create a problem.
It is a static HTML page generated from a template. Once per hour, a cron script updates the numbers and statistics. It counts the data I want to show, regenerates the page, and then the page remains static until the next run.
This is not because I cannot make a dynamic page. It is because I do not need one. Boring is good.
The homepage does not need to query all the country instances on every visit. It does not need a database request for each user who opens it. It does not need to ask snac anything in real time. The numbers are useful, but they do not need to be updated every second. Once per hour is enough, and it also fits the spirit of the whole project: do the work when it is needed, then serve the result cheaply.
I have seen too many small services become heavy because the first implementation was convenient rather than appropriate. A cron job and a template are not fashionable, but they are often exactly what a page like this needs.
fedimeteo.comAnd many more.
www.fedimeteo.com
it.fedimeteo.com
uk.fedimeteo.com
jp.fedimeteo.com
us.fedimeteo.com
usa.fedimeteo.com
can.fedimeteo.com
canada.fedimeteo.com
At the beginning, it is always tempting to write one ACL after another in the HAProxy frontend. It is quick, it is explicit, and for five hostnames it is perfectly fine. But FediMeteo did not remain at five hostnames. As countries and aliases grew, a long chain of ACLs would have turned the frontend into a list of names instead of a description of how the proxy behaves.
So I moved the hostname to backend mapping into a map file:
fedimeteo.com backend_fedimeteoThe frontend then needs only one rule:
www.fedimeteo.com backend_fedimeteo
it.fedimeteo.com backend_it
uk.fedimeteo.com backend_uk
jp.fedimeteo.com backend_jp
us.fedimeteo.com backend_us
usa.fedimeteo.com backend_us
can.fedimeteo.com backend_ca
canada.fedimeteo.com backend_ca
use_backend %[req.hdr(host),field(1,:),lower,map(/usr/local/etc/fedimeteo.map,backend_fedimeteo)]This reads the
Host header, removes the port if present, lowercases the result, and looks it up in /usr/local/etc/fedimeteo.map. If nothing matches, it falls back to the main FediMeteo backend.I like this because it keeps the configuration honest. The frontend contains the policy. The map contains the data. Adding a country means adding an entry to the map and defining a backend. I do not need to make the frontend more complicated every time the service grows.
backend backend_itOne backend, one jail, one snac instance. This is exactly the same organizational principle as the rest of the project. If I need to reason about Italy, I look at the Italian jail. If I need to reason about the United Kingdom, I look at the UK jail. If one day I need to move a country elsewhere, the separation is already there.
mode http
http-reuse safe
server srv1 10.0.0.2:8001 maxconn 30backend backend_uk
mode http
http-reuse safe
server srv1 10.0.0.7:8001 maxconn 30backend backend_jp
mode http
http-reuse safe
server srv1 10.0.0.32:8001 maxconn 30
The maxconn 30 value is not a magic number. It is a ceiling. I want each small backend to have a visible limit in front of it. If something starts hammering a country instance, I prefer the pressure to appear at the HAProxy layer instead of becoming unlimited concurrent work inside snac.
http-reuse safe lets HAProxy reuse backend connections where appropriate. This is another small reduction in unnecessary work. Opening connections repeatedly is not the biggest problem in the world, but avoiding it is still better, especially when many small services sit behind the same proxy.
frontend https_inTLS defaults are set globally:
bind :::443 v4v6 ssl crt /usr/local/etc/certs/ alpn h2,http/1.1
mode http
option http-keep-alive
ssl-default-bind-ciphersuites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256Port 80 only redirects to HTTPS, except for Let's Encrypt challenges:
ssl-default-bind-options no-sslv3 no-tlsv10 no-tlsv11 no-tls-tickets
acl letsencrypt-acl path_beg /.well-known/acme-challenge/In the HTTPS frontend I also set the usual forwarding headers:
http-request redirect scheme https code 301 unless letsencrypt-acl
use_backend letsencrypt-backend if letsencrypt-acl
http-request set-header X-Real-IP %[src]And I add HSTS:
http-request set-header X-Forwarded-Proto https
http-response set-header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"None of this is unusual, and that is fine. The interesting parts of an infrastructure are not always the parts that should be unusual.
cache mediacacheI keep media and ActivityPub JSON separate because they are not the same kind of traffic.
total-max-size 128
max-object-size 10000000
max-age 3600
process-vary on
max-secondary-entries 12cache jsoncache
total-max-size 16
max-object-size 1000000
max-age 60
process-vary on
max-secondary-entries 12
The media cache is larger and has a longer maximum age. In FediMeteo, this mostly means the shared avatar and a few static-looking objects. Since there is intentionally almost no media, the important cached object is requested very often and remains warm.
The JSON cache is smaller and short-lived. It is there for public ActivityPub GET requests, not to store federation state forever. A 60 second cache is enough to collapse many repeated requests that arrive close together in time, without pretending that ActivityPub responses should be treated like immutable files.
This distinction is important. Caching is not one decision. It is a set of small decisions about what a response means, who can see it, how often it changes, and what happens if it is served again.
acl is_media path_end -i .jpg .jpeg .png .gif .webp .svg .ico .mp4 .webm .mp3 .ogg .wav .flac .mov .avi .mkv .m4vThen I store the result in a transaction variable:
http-request set-var(txn.is_media) bool(true) if is_mediaThe cache lookup is straightforward:
http-request cache-use mediacache if { var(txn.is_media) -m bool true }
And on the response side:http-response set-header Cache-Control "max-age=3600, public" if { var(txn.is_media) -m bool true }
http-response del-header Set-Cookie if { var(txn.is_media) -m bool true }
http-response del-header Vary if { var(txn.is_media) -m bool true }
http-response cache-store mediacache if { var(txn.is_media) -m bool true }
The Cache-Control header makes the intent explicit. Set-Cookie is removed because a public media object should not carry session information. Vary is removed because I do not want the same avatar to fragment into many cache entries because of harmless header differences.This is aggressive only if removed from its context. In this service, with this media policy, it is a reasonable choice. FediMeteo is not serving private media under these paths. It is mostly serving the same public avatar over and over.
For the same reason, I clean the request before it reaches the backend:
http-request del-header Authorization if { var(txn.is_media) -m bool true }
http-request del-header Cookie if { var(txn.is_media) -m bool true }
I would not do this globally. I do it after deciding that the request is media. Scope is what makes these rules safe.The result is exactly what I want: the shared avatar becomes an almost perfect cache object. Small, public, repeatedly requested, and served by HAProxy instead of snac.
Accept header:acl is_ap_json req.hdr(Accept),lower -m sub application/activity+jsonThis part matters because ActivityPub uses content negotiation. The same path may return HTML to a browser and JSON to a remote instance. If the proxy pretends that a URL is always one thing, it will eventually cache the wrong representation.
acl is_ap_ldjson req.hdr(Accept),lower -m sub application/ld+json
acl is_outbox path_end /outbox
acl is_get method GET
acl has_auth req.hdr(Authorization) -m found
acl has_cookie req.hdr(Cookie) -m found
So I only mark public ActivityPub GET requests as cacheable:
http-request set-var(txn.is_activitypub) bool(true) if is_get !is_outbox is_ap_json !has_auth !has_cookieThere are several decisions here, all important.
http-request set-var(txn.is_activitypub) bool(true) if is_get !is_outbox is_ap_ldjson !has_auth !has_cookie
It must be a GET, because I am not caching deliveries or anything that changes state. It must not be /outbox, because outbox collections are not the traffic I want to cache here. It must not have Authorization, and it must not have cookies, because authenticated or user-specific requests do not belong in a shared public cache.
Then the cache can be used and populated:
http-request cache-use jsoncache if { var(txn.is_activitypub) -m bool true }http-response set-header Cache-Control "max-age=60, public" if { var(txn.is_activitypub) -m bool true }
http-response cache-store jsoncache if { var(txn.is_activitypub) -m bool true }
Sixty seconds is short, but useful. Federation often creates small clusters of identical requests. A remote server fetches an actor, another fetches the same actor, something asks for the same object, something retries. I do not need to cache these responses for hours. I only need HAProxy to answer the second and third identical request during the same small burst.This is microcaching in the most practical sense. It reduces repeated work without changing the nature of the service.
acl is_short_path path_reg ^/[^/]+/s/This comes from the same observation that led me to cache snac media with nginx. snac uses static media paths, and those paths often represent the kind of public, repeatable traffic that should not consume backend threads if the proxy can serve it. I call them "short", not because they are, but because the first time I saw them, I thought the 's' stood for "short", not "static". The name just stuck.
http-request cache-use mediacache if is_short_path
In FediMeteo this is less central than on a normal social instance, because I deliberately do not use media except for the avatar and basic static objects. Still, the rule fits the general policy: let HAProxy handle repeatable edge work, and let snac spend its threads where they are actually needed.
Vary, but not without limitsprocess-vary onI want HAProxy to process
max-secondary-entries 12
Vary, because content negotiation is real, especially when ActivityPub is involved. But I also want variation to be bounded. If every slightly different header creates another cache entry, the cache becomes a complicated way to miss.For media, I remove Vary before storing the response. A shared avatar does not need to vary by Accept. For ActivityPub JSON, I am more careful because the representation matters.
Again, the important thing is not the number itself. It is the decision to make variation explicit and limited.
http-response set-header X-Cache-Status HIT if !{ srv_id -m found }
http-response set-header X-Cache-Status MISS if { srv_id -m found }
This is intentionally simple. If HAProxy selected a backend server, I call it a miss. If no backend server was selected, the response came from cache, so I call it a hit. It is not a complete observability system, but it is enough to answer the first question I usually have after changing a cache rule.Did this request reach snac?
A test can be as simple as:
curl -I https://it.fedimeteo.com/path/to/avatar.pngThe second request should be a hit.
curl -I https://it.fedimeteo.com/path/to/avatar.png
For ActivityPub JSON, the test must use the right Accept header:
curl -I \And I also want to verify that cookies and authorization prevent public caching:
-H 'Accept: application/activity+json' \
https://it.fedimeteo.com/some/activitypub/object
curl -I \A cache that works should be visible. A cache that is invisible can be correct, but it can also be silently wrong. I prefer to know.
-H 'Cookie: test=value' \
-H 'Accept: application/activity+json' \
https://it.fedimeteo.com/some/activitypub/objectcurl -I \
-H 'Authorization: Bearer fake' \
-H 'Accept: application/activity+json' \
https://it.fedimeteo.com/some/activitypub/object
filter compressionThis keeps another common responsibility at the edge. The country instances can stay focused on snac and the forecast data, while HAProxy deals with client-facing compression for HTML, JSON, and ActivityPub responses.
compression algo gzip
compression type text/css text/html text/javascript application/javascript text/plain text/xml application/json application/activity+json
There is also a local Prometheus exporter:
frontend prometheusAnd I keep internal operational paths, such as statistics and Grafana, handled before the hostname map. These are small details, but ordering matters. Special paths should be explicit and early. The hostname map is for FediMeteo routing, not for every internal tool I happen to expose behind the same proxy.
bind 127.0.0.1:8405
mode http
http-request use-service prometheus-exporter
no log
The map keeps hostname routing manageable. The backend definitions keep each country isolated and limited. The static homepage avoids dynamic work for something that changes once per hour. The shared avatar gives HAProxy one very hot media object to serve directly. The media cache keeps public files away from snac. The JSON microcache absorbs short ActivityPub bursts. Header cleanup prevents useless variation. Connection reuse avoids unnecessary backend connection churn.
But all of this is only a longer way of saying one thing:
fewer requests reach snac.
That is the metric I care about here.
Not because snac is slow. If anything, FediMeteo exists in its current form because snac is efficient enough to make this kind of project possible on a very small VPS. But precisely because the whole architecture is small and pleasant, I do not want to waste resources where there is no need.
This is also consistent with the rest of the project. Forecasts are serialized by scripts. Updates happen every six hours. The homepage is regenerated hourly. Countries live in separate jails. Snapshots and backups are handled outside the application. No single component tries to be the entire system.
HAProxy is just another small piece, but it sits in the right place to remove a lot of repeated work.
It matches FediMeteo as it is now: almost no media, one shared avatar, static homepage, public forecasts, many small snac instances, and ActivityPub traffic that can benefit from a short public cache when there are no cookies or authorization headers.
If I decide one day to use media in forecasts, the media cache rules will need to be reviewed. If I use different avatars for each city or country, the cache will still work, but I will lose the very nice property of one shared, always-hot avatar. If ActivityPub responses become actor-dependent, public JSON caching must be reconsidered. If one country grows a very different traffic pattern from the others, it may deserve a different limit or policy.
This is why I do not like presenting configurations as magic. A good configuration is a written form of the assumptions behind a service. When the assumptions change, the configuration must change too.
The HAProxy layer follows this idea. It terminates TLS, routes hostnames through a map, reuses backend connections, serves the shared avatar from cache, microcaches public ActivityPub JSON, avoids authenticated and cookie-based traffic, and gives me a small diagnostic header to see what is happening.
There is no single brilliant directive here. There is only the usual work of matching infrastructure to reality.
FediMeteo publishes weather forecasts as text and emoji. The homepage is static HTML updated every hour. The accounts share the same avatar because it is enough, and because it is better for the cache. Each country has its own snac instance in its own FreeBSD jail. HAProxy stands in front of them and tries, quietly, not to bother them unless it has to.
I like this kind of infrastructure.
Not because it is invisible, but because when it works well, it leaves very little to say.
https://it-notes.dragas.net/2026/05/18/fedimeteo-haproxy-and-the-art-of-not-wasting-snac-threads/
#ITNotes #NoteHUB #fediverse #freebsd #haproxy #hosting #jail #networking #ownyourdata #server #snac #snac2 #social #web
Here is the CPU usage graph for the last 24 hours of the FediMeteo VM. A full 24 hours, during which a huge number of people are connecting, helped by the traction gained from being among the top stories on Hacker News and Lobsters, as well as the many shares across the Fediverse.
RAM usage? Active, around 450 MB. Then there is cache, ARC, and so on. But in practice, zero swap in use after days of uptime.
39 jails running, 39 snac instances, nginx serving the homepage, and HAProxy. HAProxy caching enabled. ZFS snapshots every 15 minutes, backups via zfs send and receive every hour. The same hourly schedule applies to the recalculation of cities, countries, and followers for the homepage.
All of this on a 4 euro per month FreeBSD VM.
If anyone has doubts about the quality and efficiency of FreeBSD, this is the data to show.
This morning, as the zfs-send/receive had finished its job during the night, I performed the last sync and moved FediMeteo from the previous 4 euros/month VPS - netcup - to a 4 euros/month VPS - OVH, Milano, Italy.
Thanks to #BastilleBSD and the jail setup, it was easy peasy.
So, the weather forecasts are now broadcast from Italy and the performance has skyrocketed - while still being served by a 4 euro/month VPS.
I suspect the netcup VM had been capped by the provider - but I'll investigate.
So...Ciao, FediMeteo!
In the past few days FediMeteo seemed to be having some performance trouble. I dug into it and only found minor issues, until I realised the VM itself had fallen off a cliff. After several reboots it became clear that both bandwidth and I/O latency had dropped to absurd levels. I suspect the provider slapped a cap on it.
So I took the chance to move everything to another VM and provider, still at 4 euro per month. And starting today, forecasts will be delivered straight from Italy. The performance jump feels like going from a storm to clear skies.
FediMeteo’s mission goes on. More countries are coming (stay tuned!) and we will keep aiming to serve everything from a 4 euro VM. I do have powerful hardware available, but proving that the project can run on tiny resources is still part of the mission.
#FediMeteo #FediMeteoAnnouncements #FediMeteoServices #VM #RunBSD #FreeBSD
Static Web Hosting on the Intel N150: FreeBSD, SmartOS, NetBSD, OpenBSD and Linux Compared
Update: This post has been updated to include Docker benchmarks and a comparison of container overhead versus FreeBSD Jails and illumos Zones.
#ITNotes #freebsd #illumos #jail #linux #netbsd #openbsd #ownyourdata #server #smartos #sysadmin #zoneshosting
This Isn't a Battle
After reading a post describing the FreeBSD community as 'toxic', I share a different perspective. This isn't a battle. It's a reflection on coexistence, the original Open Source spirit, and the quiet richness of taking a different path.
https://my-notes.dragas.net/2025/11/14/this-isnt-a-battle/
#MyNotes #IT #SysAdmin #FreeBSD #NetBSD #OpenBSD #Linux #OpenSource
Some technical details for those interested:
The entire FediMeteo setup runs on a FreeBSD VM costing around 4 euros per month. It supports almost all major EU countries (plus the UK), with just a few left to complete. Currently, there are 25 separate jails, each running its own instance of snac, totaling 25 instances. The VM load typically stays around 10%, which increases to 30% when updates are published for countries with larger numbers of cities (currently Germany and Italy). The only time the load spikes is when new countries are announced; during that time, all remote instances connect to all cities to download their details.
As for RAM usage, excluding the ZFS cache, it's currently a total of 213 MB. Yes, MB.
Client: Help, emergency. I have 24 hours to move my workload to another server. What do we do?
Me, five minutes later: "Done. Your workload is now running on the new server."
Client: "How did you move over 200GB with just a minute of downtime, from one provider to another and in a different country?"
Me: "Thanks to FreeBSD, ZFS, and a little bit of proactive planning."
I have a task that replicates all the VMs from one server to another every 15 minutes using zfs-send/zfs-receive. This VM connects to a VPN with two reverse proxies.
Meaning, when I move this VM, we don’t need to change any IPs since it’s not directly exposed.
I powered it off, cloned the differences in seconds, and restarted it.
Client in disbelief.
Me, relaxed and happy.
Thank you, FreeBSD, thank you, ZFS!
#FreeBSD #ZFS #TechSupport #ServerMigration #OpenZFS #SysAdmin #RunBSD
Announcing FediMeteo – Weather in the Fediverse!
UPDATE: I have created an account for updates and other information on FediMeteo - follow the account @admin to stay updated!
UPDATE: Ireland, Poland, Portugal and Switzerland have just been added
Weather has always influenced our lives: from agriculture to outdoor activities, to extreme events that, thanks to modern technology, can now be predicted with greater reliability. Personally, weather plays a significant role in my daily decisions, which is why I decided to create a service tailored for the Fediverse.
FediMeteo uses Open-Meteo data to publish updates every 6 hours, including current weather conditions, forecasts for the next 12 hours, and predictions for the upcoming days. Each country is served by its own dedicated instance (e.g., it.fedimeteo.com for Italy), managed through snac to ensure simplicity and efficiency in publishing.
You can follow FediMeteo directly in the Fediverse (on Mastodon and compatible platforms), via RSS, or by visiting the dedicated page for your city (e.g., fr.fedimeteo.com/paris).
Currently supported countries include:
Austria, Germany, France, Ireland, Italy, Netherlands, Poland, Portugal, Spain, Switzerland and the United Kingdom, – with many more regions coming soon!
FediMeteo is hosted on a FreeBSD-based VPS, with each country isolated in its own jail to ensure security and scalability.
Visit the main site to explore the national instances and start following your local weather updates today:
https://fedimeteo.com
Happy weather monitoring to all! 🌦️
FediMeteo is dedicated to my grandfather, who every evening would give me the weather forecast based on TV, radio, and his personal experience. He would convince me that the weather would be bad, so he had an excuse to accompany me to school instead of me going alone.
#FediMeteo #Announcements #FreeBSD #FediMeteo #WeatherForecasts #Weather #Meteo #snac #Fediverse #Mastodon
Right so my personal #snac instance seems to be working ok and I have managed to import all of the accounts I follow here on bsd.cafe . I'll still be using this account but will try and see how I get on with snac. You may notice that it always shows that I have no followers and that I'm not following anyone. This is intentional by the author of #snac as they feel numbers should not matter which is quite true. Feel free to follow me over there if you haven't already and hello to any new followers.
@justine@snac.smithies.me.uk
All of this is hosted in my #HomeLab on a #FreeBSd server jail running over my home FTTP connection. I'm impressed I've gotten this far. Next I'll be doing some html and css customisation's to theme it a little.
**BSD Mail Project Update!**
Hello everyone! I wanted to share some exciting updates about the development of BSD Mail, our privacy-focused email service designed with robustness, security, and transparency in mind. Here’s a deep dive into the technical choices I've made, focusing on my use of open source solutions and open protocols:
🌍 **Servers & Location**
- We're running on two physical servers:
- One hosted by OVH in France
- Another by Hetzner in Germany
- Both servers operate on FreeBSD with NVMe drives in a ZFS mirror configuration for speed and data integrity.
🔒 **Virtualization & Security**
- We utilize jails on both servers to ensure isolated environments for different services, managed via BastilleBSD. On one server, jails are set up directly on the hardware, whereas the other server employs nested jails.
- Each server hosts a bhyve VM running OpenBSD with OpenSMTPD for handling SMTP duties securely.
🔗 **Networking**
- A Wireguard setup connects the two servers, facilitating routing capabilities so that jails and VMs can communicate seamlessly, supporting both IPv4 and IPv6.
📧 **Email Services**
- **Dovecot** is configured for maildir replication across the servers using Dovecot sync, ensuring email availability and redundancy.
- **Rspamd** instances are tied to local KeyDB jails, set up in master-master replication for consistent and reliable spam detection and greylisting.
- **ClamAV** runs in corresponding jails for virus scanning, maintaining a high level of security.
- **SOGo** provides a web interface for email management, connected to MySQL databases in master-master replication to handle sessions and authentication smoothly.
💾 **Data Management**
- Email data is stored on separate, encrypted ZFS datasets to secure emails at rest.
- MySQL databases are used for storing credentials and managing sessions for SOGo, also in a master-master replication setup. Importantly, all passwords are securely hashed using bcrypt, ensuring they are salted and safe.
🔎 **Monitoring & Reliability**
- Our DNS is managed through BunnyNet, which continuously monitors our server status. Should one server—or a specific service—become unavailable, DNS configurations are dynamically adjusted to avoid directing users to the affected IP until full service is restored.
🌐 **Commitment to Open Source and Open Protocols**
- Every component of BSD Mail is built exclusively using open source software and open protocols. This commitment is crucial for ensuring data freedom and the reliability of the solutions we use.
This setup not only emphasizes our commitment to privacy and security but also our dedication to maintaining an open and transparent platform.
We're excited to bring you a service where your privacy, data integrity, and freedom are prioritized. Stay tuned for more updates!
#BSDMail #OpenSource #Privacy #FreeBSD #OpenBSD #EmailHosting #Email