No description
Find a file
2013-03-04 03:33:54 -08:00
.gitignore Added .vagrant files to a .gitignore, i.e. telling git to not track .vagrant temporary files 2013-03-04 03:33:54 -08:00
LICENSE Added MIT LICENSE to the project 2013-03-03 02:11:17 -08:00
README.md Made some further addendums to README file well as renamed the hosts in the zeromq playbook, and the guests in the Vagrantfile. I could create a local Ansible playbook which would copy public SSH keys to all of the hosts, automatically. 2013-03-04 03:30:09 -08:00
Vagrantfile Made some further addendums to README file well as renamed the hosts in the zeromq playbook, and the guests in the Vagrantfile. I could create a local Ansible playbook which would copy public SSH keys to all of the hosts, automatically. 2013-03-04 03:30:09 -08:00
zeromq.md A tad bit more formatting 2013-03-03 03:39:57 -08:00
zeromq.yml Made some further addendums to README file well as renamed the hosts in the zeromq playbook, and the guests in the Vagrantfile. I could create a local Ansible playbook which would copy public SSH keys to all of the hosts, automatically. 2013-03-04 03:30:09 -08:00

Ansible Playbooks

Configure servers in a snap with these concise Ansible playbooks!

Current Playbooks:

  • ZeroMQ - open source high-performance asynchronous messaging library

Future Playbooks:

  • MongoDB - open source document-oriented database system
  • MySQL - open source relational database system
  • Apache - open source web server
  • NginX - open source web server
  • Python - open source highlevel interprited programming language
  • Ruby - open source highlevel interprited programming language
  • RVM - open source Ruby version and environment manager

Before running these Ansible playbooks, or any Ansible commands for that matter, it is essential that you have your publick SSH keys copied to your server's ~/.ssh/authorized_keys file. The following command will copy your public key from your management computer, to the server:

# Don't space out and forget to ensure that you replace the username and ip/host address with your specific credentials.
$ scp ~/.ssh/id_rsa.pub username@111.222.333.444:~/.ssh/authorized_keys

Then all you have to do, as long as you have properly installed Ansible, and have added it's location to your $PATH, is run the following command to confirm that everything is hunky-dory:

$ ansible all -m ping

That should tell you whether Ansible has the ability to contact, and SSH into, the servers that you've added to your Ansible hosts file in /etc/ansible/hosts

It's that simple.