How to only allow loopback addresses to access the path /metrics, in Caddy.

#Caddy #Caddy2 #CaddyServer

Ich habe gerade meinen eigenen #Joplin Server aufgesetzt.
Getestet habe ich den Server durch das Erstellen einer Notiz, wie man einen Joplin Server mit #Docker und #Caddy2 aufsetzen kann. Diese Notiz will ich euch natürlich nicht vorenthalten:

https://joplin.jyrgi.de/shares/tgghxmWH6jenkUGT0x397N

#selfhosting #docker #joplin #caddy

Setup Joplin Server w/ Docker - Joplin Server

Ich habe #Caddy2 https://caddyserver.com/ entdeckt. Es gab mir den Anstoß endlich ordentliche #LetsEncrypt Zertifikate im LAN zu verteilen und statt Port-Nummern haben die Services jetzt FQDN.

...und da ich's IEL niemanden erzählen kann, der versteht, wieviel einfacher vieles geworden ist, mach ich's hier.

Caddy - The Ultimate Server with Automatic HTTPS

Caddy is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go

Caddy Web Server

Killed a couple of hours in the #homelab trying to put something behind my #caddy2 reverse proxies just to find out that I fat figured the fucking hostname!!! I almost threw myself against a wall.

#selfhosted #selfhosting

Below you will find yet another technical decision of The Liberated Edge that expands on how Internet Gateways forward HTTP request and responses to/from applications self hosted on The Edge.

Check it out and get to know what problem we aimed to solve and how Caddy 2 helped us.

https://www.theliberatededge.org/en/knowing-the-liberated-edge/architecture-and-design/caddy2-https-reverse-proxy

Please, boost this post and more people will share and learn from our experience.

Follow The Liberated Edge to always ride the tide and run safely on The Edge ;-)!

#theedge #theliberatededge #opensource #selfhosting #homelab #caddy2 #caddy #reverseproxied
Forwarding HTTP requests and responses

Caddy 2 as a reverse proxy

The Liberated Edge
Woohoo! I finally got the #caddy2 server working on my #wsl2 #debian development installation! I've been banging my head against the wall with this off and on since August, so while it may not mean much to anyone else, it's a big step forward for me personally
I'm building a low-traffic web app with #PHP, #Caddy2, and #SQLite. The database will be read-only for the web users. I can't decide whether I should put Caddy2 and PHP in the same #Docker container or use two separate containers. Is this a situation where convenience and practicality collides with "best practice"? What does the crowd think?

J'aimerais créer un playbook #ansible me permettant de configurer Caddy2. Je vois dans la doc qu'ils conseillent d'utiliser l'API parce que plus puissante que les Caddyfile. Ok, mais je ne comprends pas très bien comment rendre mon playbook idempotent (= comment je sais si la config a été modifiée ?)

Et je n'ai pas beaucoup d'expérience avec #Caddy2, donc il y a sûrement un truc qui m'échappe…

Est-ce qu'il y en a parmi vous qui ont déjà été confronté.es à ce problème ? Vous avez fait comment ?

設定とか迷ったのでQiitaに書いておくかな。
#Caddy2 に対応した情報そんなになかったし