#Tag
Just some initial memory comparisons between my two tiny VPS servers - one running httpd/relayd on OpenBSD, the other running Caddy on Alpine Linux:
OpenBSD: 99M / 464M
Alpine: 50M / 464M
Both instances are hosting 3-4 simple, static websites. Interesting stuff (to me at least!)
Just some initial memory comparisons between my two tiny VPS servers - one running httpd/relayd on OpenBSD, the other running Caddy on Alpine Linux:
OpenBSD: 99M / 464M
Alpine: 50M / 464M
Both instances are hosting 3-4 simple, static websites. Interesting stuff (to me at least!)
ICYMI, our gentle introduction to #Caddy last month, including how to use it as a low-rent red team reverse proxy!
ICYMI, our gentle introduction to #Caddy last month, including how to use it as a low-rent red team reverse proxy!
It would be amazing if all browsers rendered Markdown.
My websites and blogposts would just be Markdown files.
Just ssh/rsync and text files. No more static site generator.
Bliss.
(Yes, I know that Markdown is designed to look okay as-is. To geeks, it just about does. Yes, I could handwrite all the HTML. Yes, I am aware that there are multiple flavours of Markdown.)
@neil
Not the browser rendering Markdown but #Caddy webserver does support rendering Markdown files as web pages. I've used #caddy for many years, solid web server.
Example configuration:
https://til.jakelazaroff.com/caddy/serve-markdown-files-as-html/
Caddy doc's:
https://caddyserver.com/docs/
Made my FreeBSD server at Netcup ready to host multiple isolated applications with automatic https via Let's Encrypt.
Internet → Server → PF firewall → Caddy jail (reverse proxy) → Individual application jails
Each app gets its own isolated jail for security, while Caddy handles all the routing and https. PF keeps the front door locked.
All of course with IPv6 first, where every Jail has it's own public IP address and using NAT for legacy IPv4.
Love how FreeBSD jails make this kind of segmentation so elegant.
Made my FreeBSD server at Netcup ready to host multiple isolated applications with automatic https via Let's Encrypt.
Internet → Server → PF firewall → Caddy jail (reverse proxy) → Individual application jails
Each app gets its own isolated jail for security, while Caddy handles all the routing and https. PF keeps the front door locked.
All of course with IPv6 first, where every Jail has it's own public IP address and using NAT for legacy IPv4.
Love how FreeBSD jails make this kind of segmentation so elegant.
A space for Bonfire maintainers and contributors to communicate
