Second-Largest Olive Oil Production Complex in the Roman Empire Discovered in Tunisia

https://www.labrujulaverde.com/en/2025/11/second-largest-olive-oil-production-complex-in-the-roman-empire-discovered-in-tunisia/

> #Excavations led by Ca’ Foscari University of #Venice in ancient #Roman #Cillium, a border area of #Tunisia near present-day Algeria, are uncovering imposing structures linked to #olive oil production, among which stands out, due to its colossal dimensions, a #torcularium identified as the second-largest...
#Archaeology

#homelab update. More updates on playing with #kubernetes

1. #Cillium is like gravity: every time I come across some networking related technology I want to play with, Cillium has an implementation. It seems like the "obvious" choice for just about every networking question I have. I chose Flannel as my CNI because it seemed like the sensible option, but now I'm going to convert the cluster to Cillium and enable a bunch of it's addons.
2. #Terraform seems like overkill when used with Kubernetes. I learned it by using it to manage AWS resources at work and Terraform is a massive force-multiplier when managing that sort of stuff. For Kubernetes and Helm it almost gets in the way.
3. Following on from the previous point, all the Kubernetes APIs I've dealt with seem to be really well thought out and sensibly integrated. "How do I refer to that thing over there?" "Just give it a name then put that name here". Labels, services, daemonsets, pods, ingresses, gateways, secrets, etc. are stuff I barely understood a couple of weeks ago and I can see how to build out the stuff I want with these pretty clearly just from reading the documentation. In my experience with AWS, the best way to understand how to make a thing that works is to start building then hack at it until it works.
4. The documentation. It's a double-edged sword: everything seems to be so well designed that documentation _can_ be minimal, but also I can't find an obvious way from "here's how to use this thing" to "here's an exhaustive listing of everything you can do with this thing".

I'm glad I started down this path and I should be able to craft a bunch of "something"s to replace nearly everything I currently have running on VMs, and should be able to cover all my needs and more into the future.