How's services are configured in #docker containers managed by #ansible
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.
Tim e39fe9c458 feat: New: 0x0, SearXNG, Uptime Monitor 4 weeks ago
.woodpecker feat: opennic & readme re-write (#7) 6 months ago
roles feat: New: 0x0, SearXNG, Uptime Monitor 4 weeks ago
.ansible-lint feat: opennic & readme re-write (#7) 6 months ago
.gitignore feat: mumble server 7 months ago feat: opennic & readme re-write (#7) 6 months ago
hosts feat: New: 0x0, SearXNG, Uptime Monitor 4 weeks ago
playbook_games.yml feat: minecraft 3 months ago
playbook_remote_0x1a.yml feat: New: 0x0, SearXNG, Uptime Monitor 4 weeks ago
playbook_remote_fishnet.yml feat: fishnet 8 months ago
playbook_remote_git.yml feat: New: 0x0, SearXNG, Uptime Monitor 4 weeks ago
playbook_remote_mailcow.yml fix: migrate to using mailcow.ansible-mailcow (#2) 7 months ago
playbook_remote_mumble.yml feat: woodpecker building 7 months ago
playbook_remote_nginx_site.yml feat: isso for comments (#9) 4 months ago
playbook_remote_opennic.yml feat: opennic & readme re-write (#7) 6 months ago
playbook_remote_search.yml feat: New: 0x0, SearXNG, Uptime Monitor 4 weeks ago
playbook_remote_status.yml feat: New: 0x0, SearXNG, Uptime Monitor 4 weeks ago
playbook_remote_wallabag.yml chore: cleanup & add new servers 4 weeks ago
requirements.yml fix: update to latest ansible via real docker container for ci 7 months ago

Ansible Configuration Management for

The current build status (it should always be green...)

The showcases our configuration management system utilised by

Our tech stack consists of:

  • Ansible (for configuration management)
  • Docker (for running all the contains)
  • debian/ubuntu (for underlying hosting)

Using the tech stack above enables slowbro to have:

  • to generate wildcard LE certs via for DNS
  • traefik for web ingress, routing, & authentication
  • mailcow for self-hosted e-mail
  • wallabag as a read-it-later app
  • gitea to host this git
    • woodpecker-ci for automated testing (& deployments)
    • image/registry for our own builds
  • mumble for instant voice communications
  • nginx for website hosting (
  • tor relay(s) & onion(s) for a secure & libre internet
  • (Suggest what else I should use)

Secrets are pulled in from pass

App Deployment(s)

If you have a copy of this repository and wish to build any of these services/tech stack you will need to do a couple things before deploying:

  • Install ansible & pass on your local machine and setup the secrets needed.
  • Make changes to the defaults under roles/{role}/defaults/main.yml in nearly all roles.
    • You can find what path we look for secrets in there.
  • Create your own hosts file with the servers.

Once that is done all you need is SSH access and you are ready to deploy.


After rolling my own role, mailcow actually provide an ansible role under mailcow.mailcow. So we have migrated over to that. We recommend at a minimum 4GB of ram for your mailserver. Due to rspamd (anti-spam) & clamav (anti-virus), they take up about 600M & 1.3G respectively.

ansible-playbook playbook_remote_mailcow.yml -i hosts --ask-become-pass


A great read-it-later application with solid android support.

ansible-playbook playbook_remote_wallabag.yml -i hosts

Git (Gitea/Woodpecker/Docker Registry)

ansible-playbook playbook_remote_git.yml -i hosts


ansible-playbook playbook_remote_mumble.yml -i hosts

Extra Services:


Fishnet is a distributed service to help run their analysis of the Stockfish engine. We contribute our excess cpu to help others improve their performace. Read more about Fishnet here:

ansible-playbook playbook_remote_fishnet.yml -i hosts


We contribute back to the OpenNIC Project with multiple Tier 2 DNS resolvers.

The role utilises:

  • srvzone method for automating BIND9 updates
  • Has zero logging by default
  • Integrates the Tier 2 Security Measures via iptables for some minor form of security

We will be setting up dnscrypt/DoH/DoT in the future


If you utilise this role, it will remove all iptable INPUT rules you have and replace then with only allowing SSH & DNS queries. Use at your own risk! I welcome a more efficient solution for this problem. If you have any ideas please feel free to contact me.

ansible-playbook playbook_remote_opennic.yml -i hosts


We run tor relays on nearly all systems to contribute back our excess bandwidth If you use our common role, you are also contributing!