techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.6K
active users

#caddy

1 post1 participant0 posts today
Sharlatan<p><span class="h-card" translate="no"><a href="https://babka.social/@kolev" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kolev</span></a></span> It reminded me that we may complete packaging <a href="https://mastodon.social/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> after the go-team is merged</p><p><a href="https://issues.guix.gnu.org/78781" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">issues.guix.gnu.org/78781</span><span class="invisible"></span></a></p>
Crawford Long<p>I never in my wildest dreams imagined that adding <a href="https://mastodon.social/tags/authelia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>authelia</span></a> website authentication to a site via <a href="https://mastodon.social/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a> would be anything other than routine and mundane, and yet it has utterly broken me. Thrust me in to a world of infinite loops, "headers too big" and, hilariously, working on one computer and not on another, then switching places.</p><p>I have discovered madness.</p><p><a href="https://mastodon.social/tags/nixos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nixos</span></a> <a href="https://mastodon.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a></p>
panigrc<p><span class="h-card" translate="no"><a href="https://social.k3can.us/@me" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>me</span></a></span> Also change your <a href="https://mastodon.social/tags/webserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webserver</span></a> configuration to support <a href="https://mastodon.social/tags/http2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http2</span></a> this will make the multiple requests much faster.</p><p><a href="https://mastodon.social/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a> for example supports http2 out of the box</p>
Rafael Kassner<p>I made a thing!</p><p><a href="https://github.com/kassner/caddy-trapdoor" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kassner/caddy-trapd</span><span class="invisible">oor</span></a></p><p>A Caddy module to temporarily block web scrapers sending tons of requests at once.</p><p><a href="https://phpc.social/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> <a href="https://phpc.social/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a> <a href="https://phpc.social/tags/webserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webserver</span></a></p>
panigrc<p><span class="h-card" translate="no"><a href="https://mastodon.social/@ivantodorov" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ivantodorov</span></a></span> then you are going to love <a href="https://mastodon.social/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a> because it works out of the box</p>
日落<p>Cadyy 的設定檔也簡單的太不像話了,這樣就沒有認真工作的感覺</p><p><a href="https://social.zeroplex.tw/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a></p>
:projetstodon: Shalien<p>Dear <a href="https://mastodon.projetretro.io/tags/fediadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fediadmin</span></a>, regarding the current ongoing full force assault on our services by AI scrappers with all the risks associated (costs, services stability, data being stolen and so on) I can only recommend the setting up of <a href="https://mastodon.projetretro.io/tags/techaro" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>techaro</span></a> <a href="https://mastodon.projetretro.io/tags/anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>anubis</span></a> requests filter to "weight the souls of incoming HTTP requests"</p><p>I tested it so far on <a href="https://mastodon.projetretro.io/tags/alpine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>alpine</span></a> <a href="https://mastodon.projetretro.io/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debian</span></a> deployed services with either <a href="https://mastodon.projetretro.io/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a> , <a href="https://mastodon.projetretro.io/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>apache2</span></a> / <a href="https://mastodon.projetretro.io/tags/httpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>httpd</span></a> and <a href="https://mastodon.projetretro.io/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nginx</span></a> for the following services <a href="https://mastodon.projetretro.io/tags/nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nextcloud</span></a>, <a href="https://mastodon.projetretro.io/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastodon</span></a>, <a href="https://mastodon.projetretro.io/tags/forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>forgejo</span></a>, <a href="https://mastodon.projetretro.io/tags/lemmy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lemmy</span></a>, <a href="https://mastodon.projetretro.io/tags/funkwhale" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>funkwhale</span></a>, <a href="https://mastodon.projetretro.io/tags/bookwyrm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bookwyrm</span></a> and a <a href="https://mastodon.projetretro.io/tags/minecraft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>minecraft</span></a> <a href="https://mastodon.projetretro.io/tags/mapviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mapviewer</span></a> with little hassle and no big issues</p><p>Following the use of <a href="https://mastodon.projetretro.io/tags/anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>anubis</span></a>, all scrapper (AI and regular) logs dropped drastically and bandwitch usage was cut by two third on the mastodon instance and half for the others services</p><p>Do yourself and your users a favor try it : <a href="https://github.com/TecharoHQ/anubis" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/TecharoHQ/anubis</span><span class="invisible"></span></a></p>
aaron ~# :blinkingcursor:<p><a href="https://infosec.exchange/tags/OpenWRT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenWRT</span></a> on a <a href="https://infosec.exchange/tags/Fritzbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fritzbox</span></a> is kinda pain since there are so many things i could technically do if the fritzbox had more powerful hardware. Can't wait to build my own router. </p><p>A <a href="https://infosec.exchange/tags/Fujitsu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fujitsu</span></a> <a href="https://infosec.exchange/tags/Thinclient" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Thinclient</span></a> S920 would be a perfect fit and is also cheap as hell.</p><p>More powerful hardware would allow me to take advantage of <a href="https://infosec.exchange/tags/tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tor</span></a> <a href="https://infosec.exchange/tags/routing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>routing</span></a>, local <a href="https://infosec.exchange/tags/tailscale" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tailscale</span></a> resolving, <a href="https://infosec.exchange/tags/adblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>adblocking</span></a> and much more. Maybe even some <a href="https://infosec.exchange/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> <a href="https://infosec.exchange/tags/containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>containers</span></a> like <a href="https://infosec.exchange/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a>.</p><p><a href="https://infosec.exchange/tags/OpenWRT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenWRT</span></a> is a real <a href="https://infosec.exchange/tags/gamechanger" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gamechanger</span></a> for my <a href="https://infosec.exchange/tags/homenetwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homenetwork</span></a>.</p><p><a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://infosec.exchange/tags/freeandopensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freeandopensource</span></a> <a href="https://infosec.exchange/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>network</span></a> <a href="https://infosec.exchange/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://infosec.exchange/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>firewall</span></a></p>
panigrc<p><span class="h-card" translate="no"><a href="https://cyberfurz.social/@hack13" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>hack13</span></a></span> I have a <a href="https://mastodon.social/tags/wireguard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wireguard</span></a> entrypoint in a <a href="https://mastodon.social/tags/vps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vps</span></a> and connect through it to my <a href="https://mastodon.social/tags/homeserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homeserver</span></a> <br>Currently have:<br><a href="https://mastodon.social/tags/pihole" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pihole</span></a><br><a href="https://mastodon.social/tags/homeassistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homeassistant</span></a><br><a href="https://mastodon.social/tags/esphome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>esphome</span></a><br><a href="https://mastodon.social/tags/mstream" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mstream</span></a><br><a href="https://mastodon.social/tags/gonic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gonic</span></a><br><a href="https://mastodon.social/tags/WoodpeckerCI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WoodpeckerCI</span></a> worker</p><p>And <a href="https://mastodon.social/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a> as reverse proxy</p><p><a href="https://mastodon.social/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://mastodon.social/tags/selfhost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhost</span></a> <a href="https://mastodon.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a></p>
Lucas Janin 🇨🇦🇫🇷<p><span class="h-card" translate="no"><a href="https://kolektiva.social/@rae" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>rae</span></a></span> This is the way! </p><p>My setup is very similar to your plan. I have 4 VMs on my public VLAN: <a href="https://mastodon.social/tags/Headscale" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Headscale</span></a>, <a href="https://mastodon.social/tags/PocketID" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PocketID</span></a>, Podsync and <a href="https://mastodon.social/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> as a reverse proxy. </p><p>Like your plan, all my other services are only accessible via <a href="https://mastodon.social/tags/Tailscale" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tailscale</span></a>. So, I cut the Tailscale server dependency</p>
Ivan Agosto 🇲🇽<p><a href="https://mast.lat/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> funciona muy bien si estas pensando autoalojar servicios. Es un server que puede funcionar de proxy inverso (para eso lo uso).</p><p>Hoy configure Caddy para que muestre un mensaje cuando mi blog este caido como hoy que se fue la luz.</p><p>Si aun no sabes que es caddy te dejo su sitio oficial:<br><a href="https://caddyserver.com/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">caddyserver.com/</span><span class="invisible"></span></a></p>
Martin Boller :debian: :tux: :freebsd: :windows: :mastodon:<p>Another short blog post on blocking <a href="https://infosec.exchange/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://infosec.exchange/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLM</span></a> <a href="https://infosec.exchange/tags/Bots" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bots</span></a> that slow down a website. Using <a href="https://infosec.exchange/tags/NGINX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NGINX</span></a>, but easily adaptable to <a href="https://infosec.exchange/tags/ApacheWebServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ApacheWebServer</span></a> <a href="https://infosec.exchange/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> etc</p><p><a href="https://www.infosecworrier.dk/blog/2025/07/botblocker/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">infosecworrier.dk/blog/2025/07</span><span class="invisible">/botblocker/</span></a></p>
Gea-Suan Lin<p><a href="https://blog.gslin.org/archives/2025/07/04/12498/caddy-%e4%b8%8a%e7%94%a8-dnsbl-%e6%93%8b-bot/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.gslin.org/archives/2025/0</span><span class="invisible">7/04/12498/caddy-%e4%b8%8a%e7%94%a8-dnsbl-%e6%93%8b-bot/</span></a></p><p>Caddy 上用 DNSBL 擋 bot</p><p><a href="https://abpe.org/tags/address" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>address</span></a> <a href="https://abpe.org/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ai</span></a> <a href="https://abpe.org/tags/bot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bot</span></a> <a href="https://abpe.org/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a> <a href="https://abpe.org/tags/dnsbl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dnsbl</span></a> <a href="https://abpe.org/tags/ip" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ip</span></a> <a href="https://abpe.org/tags/proxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxy</span></a> <a href="https://abpe.org/tags/spam" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spam</span></a> <a href="https://abpe.org/tags/wiki" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wiki</span></a></p>
Uckermark MacGyver :nonazi:<p>Switched this server to my new <a href="https://hub.uckermark.social/tags/Hetzner" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hetzner</span></a> Object Storage backend. Also switched from <a href="https://hub.uckermark.social/tags/NGINX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NGINX</span></a> as reverse proxy to <a href="https://hub.uckermark.social/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a>.</p>
OpenUEM<p>If you want to deploy OpenUEM with Docker now you have the option to use a <a href="https://mastodon.social/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> container as a reverse proxy included in the compose file <a href="https://openuem.eu/docs/Installation/Server/docker/#3-use-a-reverse-proxy-optional" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">openuem.eu/docs/Installation/S</span><span class="invisible">erver/docker/#3-use-a-reverse-proxy-optional</span></a> Thanks <span class="h-card" translate="no"><a href="https://birdsite.kohl.dev/users/caddyserver" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>caddyserver</span></a></span></p>
Haruka<p>A new article on my <a href="https://mamot.fr/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blog</span></a>, about installing and configuring <a href="https://mamot.fr/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> the web server I use now instead of Apache and Nginx.<br><a href="https://memcat.eu/2025/caddy" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">memcat.eu/2025/caddy</span><span class="invisible"></span></a></p><p><span class="h-card" translate="no"><a href="https://infosec.exchange/@caddy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>caddy</span></a></span></p>
patpro<p>Hello, I’m hosting a <a href="https://social.patpro.net/tags/vaultwarden" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vaultwarden</span></a> server behind <a href="https://social.patpro.net/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> 2.10 and made the following test:</p><p>Tuning Caddy to allow only <a href="https://social.patpro.net/tags/pqc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PQC</span></a> curves:</p><pre><code> tls { curves x25519mlkem768 } </code></pre><p>Trying to connect with <a href="https://social.patpro.net/tags/firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a> Mac -&gt; OK<br>Trying to connect with <a href="https://social.patpro.net/tags/bitwarden" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bitwarden</span></a> <a href="https://social.patpro.net/tags/android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>android</span></a> client -&gt; Fail</p><p>Without the <a href="https://social.patpro.net/tags/tls" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TLS</span></a> tuning, the Bitwarden Android client will happily connect to the server.</p><p>Is it a problem with the Bitwarden Android client or with Android, or both?</p>
Lucas Janin 🇨🇦🇫🇷<p>This week I learned to deploy <a href="https://mastodon.social/tags/Crowdsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Crowdsec</span></a> in my <a href="https://mastodon.social/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a>:</p><p>- CrowdSec LAPI on an LXC in my private VLAN <br>- Caddy-bouncer to protect my public servives<br>- CrowdSec-firewall-bouncer-iptables on my 2 <a href="https://mastodon.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Proxmox</span></a> nodes <br>- CrowdSec agent for all my public VMs and important VMs/LXCs </p><p>Of course, I created an <a href="https://mastodon.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ansible</span></a> role to deploy the agent on my multiple hosts/VMs/LXCs using a certificate and a custom port, 8080 is a busy port :-)</p><p>Yes, it’s overkill :-)<br><a href="https://mastodon.social/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://mastodon.social/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> <a href="https://mastodon.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://mastodon.social/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caddy</span></a></p>
Shane Rogers<p><a href="https://social.lol/tags/Yesterday" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Yesterday</span></a> I was able to get my <a href="https://social.lol/tags/MailcowDockerized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MailcowDockerized</span></a> box to work behind the <a href="https://social.lol/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> reverse proxy. A lot easier than I anticipated.</p><p>I may have to reconfigure my mobile <a href="https://social.lol/tags/Thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Thunderbird</span></a> client - for some reason it's not sending to outlook365, but SoGo does just fine.</p><p><a href="https://social.lol/tags/Today" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Today</span></a> I'm thinking about getting a static site to sit behind that caddy proxy. I'd like to get <a href="https://social.lol/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>emacs</span></a> and <a href="https://social.lol/tags/org" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>org</span></a> working for publishing.</p><p>So far, so good. Slow going.</p>
Bradley Taunt<p>I'm in the process of porting over all OpenBSD related mini-sites to <a href="https://mastodon.bsd.cafe/tags/httpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>httpd</span></a> running on my TinyKVM VPS.</p><p>All other web projects will be migrated to Alpine <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>, served through <a href="https://mastodon.bsd.cafe/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Caddy</span></a> on my other VPS.</p>