Ansible role for setting up a Rookeries instance.
Go to file
Dorian 5c8402c98e Move rookeries installation into deployment stand-alone playbook. 2015-03-09 16:03:16 -04:00
config Add role variables to meta content itself for more flexibility. 2015-03-09 16:02:32 -04:00
defaults Initial migration to setup ansible role from provisioning steps from Rookeries. 2015-02-27 08:56:41 -05:00
handlers Initial migration to setup ansible role from provisioning steps from Rookeries. 2015-02-27 08:56:41 -05:00
meta Add role variables to meta content itself for more flexibility. 2015-03-09 16:02:32 -04:00
tasks Add role variables to meta content itself for more flexibility. 2015-03-09 16:02:32 -04:00
templates/dev_supervisor Add role variables to meta content itself for more flexibility. 2015-03-09 16:02:32 -04:00
vars Add role variables to meta content itself for more flexibility. 2015-03-09 16:02:32 -04:00
README.md Initial migration to setup ansible role from provisioning steps from Rookeries. 2015-02-27 08:56:41 -05:00
deployment.yaml Move rookeries installation into deployment stand-alone playbook. 2015-03-09 16:03:16 -04:00
requirements.yaml Migrate Ansible setup to use an external role to handle setup of the NGINX, UWSGI and supervisord setup. 2015-01-08 18:22:39 -05:00

README.md

Role Name

A brief description of the role goes here.

Requirements

Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.

Role Variables

A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.

Dependencies

A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.

Example Playbook

Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:

- hosts: servers
  roles:
     - { role: username.rolename, x: 42 }

License

AGPL v3

Author Information

An optional section for the role authors to include contact information, or a website (HTML is not allowed).