Displaying 1 to 17 from 17 results

mac-dev-playbook - Mac setup and configuration via Ansible.

This playbook installs and configures most of the software I use on my Mac for web and software development. Some things in macOS are slightly difficult to automate, so I still have some manual installation steps, but at least it's all documented here. This is a work in progress, and is mostly a means for me to document my current Mac's setup. I'll be evolving this set of playbooks over time.

ansible-role-mysql - Ansible Role - MySQL

Installs and configures MySQL or MariaDB server on RHEL/CentOS or Debian/Ubuntu servers. The home directory inside which Python MySQL settings will be stored, which Ansible will use when connecting to MySQL. This should be the home directory of the user which runs this Ansible role. The mysql_user_name and mysql_user_password can be set if you are running this role under a non-root user account and want to set a non-root user.

ansible-role-php - Ansible Role - PHP

Installs PHP on RedHat/CentOS and Debian/Ubuntu servers. If you're using an older LTS release of Ubuntu or RHEL, with an old/outdated version of PHP, you need to use a repo or PPA with a maintained PHP version, as this role only works with PHP versions that are currently supported by the PHP community.

mariadb-ansible-galera-cluster - Automated installation of MariaDB Galera Cluster using Ansible

These roles allow you to automatically setup a MariaDB Galera cluster with sane default settings.These roles are currently only tested for RHEL/CentOS 7, but most tasks can be reused for Debian or SUSE based distributions.

graylog-ansible-role - Ansible role which installs and configures Graylog

Ansible role which installs and configures Graylog log management. Take a look into defaults/main.yml to get an overview of all configuration parameters.

fedora-ansible - Ansible playbooks for Fedora

This repository contains user-contributed real world examples for Ansible playbooks, especially for Fedora and its downstream (RHEL), as well as modules that are not a part of Ansible's core distribution. This is designed to be a resource to folks learning configuring Fedora with Ansible, as well as a way to share useful resources of all kinds.

graphite-stack-ansible-vagrant - Provision a complete Graphite, StatsD & Grafana install using Ansible and (optionally) Vagrant

This playbook makes it really easy to setup Graphite, StatsD(aemon) and Grafana on a server (VPS or Dedicated). You can also optionally install it on a Virtual Machine using Vagrant so you can play around with it. It uses Ansible, a great configuration management tool written in Python, to automatically install the applications and all dependencies and configure everything to work optimally. If you want to install Graphite on a VM using Vagrant, you first need to install Vagrant and a Virtual Machine provider of choice (VirtualBox is free and works out of the box with Vagrant).

ansible-skel - Ansible skeleton to quick start

This is my Ansible skeleton. It provide a nice structure to work comfortably with Ansible. You don't need to follow all principes of this structure to use Ansible. Then add your target hosts under the [targets] section. If you feel lost, checkout the examples inside the file. Once you have done that, you can run the first playbook, which will ensure you have all required roles. If you don't have them, it will download them from Ansible Galaxy or from a git repo depending the source. It will install them into roles/vendors.

drupal-pi - Drupal on a single Raspberry Pi.

This project is an offshoot of the Rasbperry Pi Dramble project, which helps install Drupal on a cluster ('Bramble') of Raspberry Pi 2 computers. This playbook/project makes setting up Drupal on a single Raspberry Pi a very easy/simple operation.

drupalci-sonar-jenkins - Drupal CI environment with SonarQube and Jenkins for Drupal Core code analysis

This Vagrant configuration (with Ansible for provisioning) will install Jenkins, PHP, SonarQube, and Drupal CI profiles for code analysis (along with a bunch of other required software). Note for Windows users: This guide assumes you're on a Mac or Linux host. Windows support may be added when I get a little more time; the main difference is Ansible needs to be bootstrapped from within the VM after it's created. See JJG-Ansible-Windows for more information.

ansible-web-playbooks - Set of playbooks roles to orchestrate your web servers, powered by Ansible.

Set of playbook roles to orchestrate your web servers, powered by Ansible. Clone the repo, git clone git://github.com/mgcrea/ansible-web-playbooks.git, download the latest release or install with npm npm install ansible-web-playbooks.

galaxy-tools-playbook - A ready-to-use Ansible playbook for the Galaxy Tools role

A ready-to-use Ansible playbook for the Galaxy Tools role. Before you can use this playbook, you need to install Ansible (version is required). Note that for the time being, this playbook does not work with Python 3.x.

mac-playbook - Mac setup and configuration via Ansible.

This playbook installs and configures most of the software I use on my Mac for web and software development. The playbook contained in this repo does nothing except delegate all functionality to geerlingguy/mac-dev-playbook's playbook. Note: Do NOT install anything you haven't looked through–this is a highly opinionated set of configurations. Running the playbook will affect pretty much every aspect of your environment so for others than me, this is mostly a reference point.

ansible-ipsec - IPSec configuration generator for Ansible

Ansible role to enable IPSec encryption between Ansible-managed nodes with minimal performance overhead. This role is especially suitable for protecting communications between farms of cloud servers and can effectively replace the need for the complexity of configuring TLS for each service running on the servers. This role will always create IPSec configuration for full ipsec group on each host, regardless of current play scope limitation. This is to ensure that scope-limited runs don't leave some hosts with IPSec configuration and their counterparts without one, which will cause issues with the require policy.