|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Ansible Playbook Grapher||489||1||3 days ago||44||June 22, 2022||5||gpl-3.0||Python|
|A command line tool to create a graph representing your Ansible playbook tasks and roles|
|Debops Playbooks||482||6 years ago||35||other||Python|
|Ansible playbooks used by DebOps project|
|Aws Securitygroup Grapher||91||3 years ago||apache-2.0||HTML|
|This ansible role gets information from an AWS VPC and generate a graphical representation of security groups|
|Ansible Viz||28||6 years ago||14||apache-2.0||Ruby|
|Graph relationships between Ansible playbooks / roles / tasks / vars etc. via static analysis|
|Ansible Roles Graph||16||5 years ago||1||December 04, 2015||12||gpl-3.0||Python|
|Ansible Multicast Graph||13||6 years ago||2||Python|
|Visualises the multicast trees for a single IPv4 group address using information scraped from NX-OS, EOS and IOS devices using ansible, ntc-ansible and TextFSM|
|Cactilize||11||9 years ago||gpl-2.0||PHP|
|Ansible Role for deploying and maintaining cacti server and host (graph, devices, templates, tree ...)|
|Graph the benchmark output of Substrate Pallets.|
|Openstack Securitygroup Grapher||6||2 years ago||gpl-3.0||Jinja|
|This ansible role gets information from an openstack tenant and generate a graphical representation of security groups|
|Ansible Arangodb Operator||5||2 years ago||mit||Jinja|
|Ansible role and sample playbook to deploy ArangoDB Operator in a Kubernetes cluster|
This repository contains all the playbooks used by DebOps.
Fully loaded ready to go applications
Web application deployment
Service monitoring and logging
Backup and encryption
common.yml playbook which gets ran on every host except localhost.
This includes standard services like
sshd and ferm. The full list can be
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
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.
The dependency graph was generated using: ansigenome.
If you want to keep tabs on each role's status then check out our status page.