DebOps playbooks
This repository contains all the playbooks used by DebOps.
- Here are a few services that are available
- Overview of how playbooks work within DebOps
- View a dependency graph
- Status page
Here are a few services that are available
Fully loaded ready to go applications
GitLab | GitLabCI | Etherpad | DokuWiki | ownCloud | phpIPAM | Mailman |
Databases
PostgreSQL | MariaDB | Redis | Memcached | Elasticsearch |
Programming languages
Ruby | Golang | Java | NodeJS | PHP |
Web application deployment
nginx | Apache | RubyOnRails |
Service monitoring and logging
LibreNMS | monit | rsyslog |
Networking
dnsmasq | DHCP | Radvd | ferm | postfix | SMS | SSH | NFS | Samba | Tinc |
Virtualization
LXC | Docker | libvirt |
Backup and encryption
Safekeep | BoxBackup | encFS | cryptsetup | SKS | Monkeysphere |
Security
PKI | dhparam | slapd |
Overview of how playbooks work within DebOps
There's a common.yml
playbook which gets ran on every host except localhost.
This includes standard services like sshd
and ferm. The full list can be
found here.
Additional plays are then ran based on what groups the host is in. For example if you wanted
to setup a Gitlab instance you would add a host to the [debops_service_gitlab]
group
in your inventory.
That carries over for things like postgresql, ruby or any service for the most part. You can also install roles as dependencies rather than use inventory groups.
The dependency approach makes sense in a lot of places, especially for setting ports through ferm or perhaps installing a database for a role that demands that database.
You can view all of the services and plays here.
View a dependency graph
The dependency graph was generated using: ansigenome.
Status page
If you want to keep tabs on each role's status then check out our status page.