Scripts and such to automate things
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
LUXEY Adrien 3d07045b69 updated Synapse to v1.37.1 and gitea to 1.14.3 3 months ago
bootstrapper rewrote parts of the OS install guide 5 months ago
coturn_debugging debugging turn 8 months ago
deployer updated Synapse to v1.37.1 and gitea to 1.14.3 3 months ago
jitsi/ansible started jitsi conf and moved zinzoscope and lexperimental to templating solution 1 year ago
security performed a SSL security test, needs to be reviewed 1 year ago
.gitignore gitea not well configured 1 year ago
README.md guide about installing a Debian remotely with full disk encryption 7 months ago

README.md

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

Go to deployer, where the fun is at.

Structure

  • /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.

TODO

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.

Alternatives

  • 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