mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

620
comptes actifs

#caddy

1 message1 participant0 message aujourd’hui
Suite du fil

Ha! I was able to get at least Forgejo configured with Pocket ID!

I thought I had to rebuild my Caddy container simply because I was misunderstanding how to properly configure it, but I don't actually need that. Interesting enough, the solution hit me in the head while I was brushing my teeth. 😁

Okay, now let's see which other services accept OAUTH2. 🎉

Ai-je trouvé la raison pourquoi #Caddy ne fait pas mieux que #Nginx pour faire passer l'IP du client?
Ça expliquerait pourquoi dans les logs de Caddy je vois parfois les IPv4 véritables des clients et d'autres fois l'adresse IPv4 locale de la passerelle du réseau #Docker. Dans le 2e cas (celui qui ne fonctionne pas), ce serait des clients en #IPv6.
La théorie se tient en tout cas !
https://github.com/caddyserver/caddy/issues/4339

GitHubX-Forwarded-For does not contain the IP of the original caller when caddy in docker and client uses IPv6 · Issue #4339 · caddyserver/caddyPar bb

Yesterday afternoon I've given @cryptpad a try.
Even though I don't really have a use for it, I wanted to test the installation on #freebsd.

It took only few minutes to create the jail, checkout the code, make the install and tune the configuration file.
Using #caddy as a proxy was really straightforward thanks to config examples, and they even provide an rc script for freebsd.

It's been a really long time since I've seen such a smooth and well documented install process for a non-packaged software. And I'm so happy they only provide docker as an option, not as the main (or only) supported installation method.

The senior #sysadmin in me is absolutely thrilled by the work of the #cryptpad team.
As a user I think the application is well designed and achieves the very difficult balance between secure design and usability.

Great job.

Suite du fil

For caddy, I used wget and a custom subdomain.

caddy.container:
...
HealthCmd=wget --no-verbose --tries=1 --spider test.example.com/health-check || exit 1
HealthStartPeriod=10s
HealthInterval=30s
HealthTimeout=5s
HealthRetries=5
Notify=healthy
...

Caddyfile:
...
test.example.com {
respond /health-check 200
respond "Hello, world!"
}
...

Inspiration:

1) caddyserver.com/docs/caddyfile

2) caddy.community/t/what-is-the-

I'm curious to hear what others are #SelfHosting! Here's my current setup:

Hardware & OS

Infrastructure & Networking

Security & Monitoring

Authentication & Identity Management

  • Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
  • LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
    #AuthenticationTools #IdentityManagement

Productivity & Personal Tools

Notifications & Development Workflow

  • Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
  • Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote

Accessibility Focus ♿🖥️

Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign#DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!

I've also experimented with:

  • Ollama (#Ollama): Not enough RAM on my Pi.
  • Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.

I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 😄

What's your setup like? Any cool services you'd recommend I try?

#SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY

@selfhost @selfhosted @selfhosting

Bon je comprend pas du tout pourquoi j'arrive pas a avoir de certif sur mon domaine pihole ... genre j'ai accès au pihole par le domaine pi.hole je sais pas comment donc et donc le mien par caddy pihole.lan, mais impossible d'avoir un certif valide avec un joli no OCSP server specified in certificate + donc FF qui me sort un erreur de sécurité alors que pour Glance pas de soucis :nko_curious:

Je comprend déjà même pas comment l'admin page de pihole tourne vu que y a pas lighttp ni php-fpm d'installer ... a moins que tout soit dans le bin de pihole ? et donc je l'ai dans l'os ?

Note : caddy étant sur une VM a part.

#Pihole #Caddy #Lighttp

As the next step in my quest to make it easier to poison AI crawlers, I present you: OCIocaine: a project where #DockerCompose meets #Caddy and #Iocaine, to poison AI crawlers for all your sites, automatically.

The idea here is to provide a docker compose file that starts up Caddy and Iocaine, configured so that Caddy will reverse proxy for any and all services on the same docker network, as long as they have a few labels that tell it to do so. In addition, a Caddyfile snippet will be available for all of these, which takes care of routing bad visitors to Iocaine.

And if that's not enough, the whole thing comes preconfigured with a wordlist (a list of English words), and traning data (the complete works of Shakespeare), and a list of known AI crawlers (courtesy of ai.robots.txt).

All you have to do is copy the sample configuration, create a network, start it up, and deploy labeled containers into the same network, and OCIocaine takes care of the rest.

MadHouse Git RepositoriesociocaineDocker Compose meets Caddy and Iocaine to poison AI for all your sites, automatically.

Bonjour l’#ESR !

Y-a-t’il des gens parmi vous ou vos collègues qui font tourner du #Moodle via des PHP-FPM en balance de charge derrière un frontal HTTP #Caddy ?

On est sur un boitier F5 en fin de vie qui répartit la charge entre 7 nœuds Apache + php-fpm. J’aimerai explorer une piste plus simple/moderne (où les nœuds font seulement le php, et où le frontal web gère HTTP/3, le renouvellement auto de ses certificat TLS, et peut être reconfiguré à chaud, etc).

Le #boost garantit un bon W-E :)