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.
Daniel Berteaud
189c36c663
|
5 years ago | |
---|---|---|
library | 5 years ago | |
playbooks | 5 years ago | |
roles | 5 years ago | |
LICENSE | 5 years ago | |
README.md | 5 years ago | |
ansible.cfg | 5 years ago |
README.md
ansible-roles
At Firewall Services, we use Ansible. And we use it a lot. Like, there's now nearly nothing we deploy manually, without it. As such we've written a lot of roles, to deploy and manage various applications. This include :
- Basic system configuration
- Authentication (eg, configure LDAP auth, or join an AD domain automatically)
- Plumber layers (like deploy a MySQL server, a PHP stack etc.)
- Authentication services (Samba4 in AD DC mode, Lemonldap::NG etc.)
- Collaborative apps (like Zimbra, Matrix, Etherpad, Seafile, OnlyOffice, Jitsi etc.)
- Monitoring tools (deploy Zabbix agent, proxy and server, Fusion Inventory agent, Graylog server)
- Web applications (GLPI, Ampache, Kanboard, Wordpress, Dolibarr, Matomo, Framadate, Dokuwiki etc.)
- Dev tools (Deploy a Gitea server)
- Security tools (OpenXPKI, Bitwareden_RS, manage SSH keys etc.)
- A lot more :-)
Most of our roles and CentOS centric, and are made to be deployed on CentOS 7 servers. Basic roles (like basic system configuration, postfix etc.) also supports Debian systems, but are less tested.
Our roles are often dependent on other roles. For example, if you deploy glpi, it'll first pull all the required web and PHP stack.
All this is available on our GIT repo : https://git.fws.fr/fws/ansible-roles