Scripts and such to automate things
Go to file
2022-02-09 15:07:46 +01:00
bootstrapper rewrote parts of the OS install guide 2021-04-11 17:05:18 +02:00
coturn_debugging debugging turn 2021-01-29 16:09:53 +01:00
deployer closed registration to Synapse again :'( 2022-02-09 15:07:46 +01:00
jitsi/ansible started jitsi conf and moved zinzoscope and lexperimental to templating solution 2020-04-27 09:45:07 +02:00
security added info on spam sources in Synapse 2022-02-09 09:42:08 +01:00
.gitignore gitea not well configured 2020-05-07 12:47:05 +02:00 guide about installing a Debian remotely with full disk encryption 2021-03-04 12:01:33 +01:00

Automation: because 10h of coding can save 10m of your life!

Go to deployer, where the fun is at.


  • /deployer contains deployment Ansible code for Serenity. Being outdated by migration to new server (HammerHead).
  • /bootstrapper contains Ansible configuration code for new servers (notably HammerHead). Will only take interest in the bootstrapping phase of the host. Service deployment will be handled by Nomad et al.


Random notes

How to package Wordpress

Wordpress + PHP-FPM in Docker + nginx

nginx and PHP-FPM both need access to the files--at the same location. It's thus not easy to have a single nginx serving multiple PHP-FPM containers. You always need a webserver in the same container as PHP-FPM.


  • WP multisite + Caddy: arguments against using the Wordpress Docker image, keeps the whole wp install outside the image, and instead focuses on properly configuring PHP-FPM. Has the advantage of being reusable for other PHP projects. Is well argumented. Tackles file access rights and mailing (ssmtp), it's a good source!

Which webserver?

traefik does not support php-fpm, Caddy does. Not such a problem, we can keep Apache inside the container, who gives a shit.

Wordpress security