No description
Find a file
2013-04-14 02:13:21 -07:00
bottle-mongodb Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
homebrew Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
limechat Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
sublime-text Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
transmission Added Transmission playbook. Also the realization recently cemented in my brain that I can use Ansible and Jinja2 variables anywhere in a playbook, and I mean anywhere! This will greatly help with separation of logic and DRY principles as I will be able to pull out the logic of dealing with DMGs, Tars, and Zips when installing, as they all seem to be using the same formula at this point. I will have to add DMG ejection to the flow, as well as determining how to automate the removal of DMGs from disk utility. 2013-04-14 02:13:21 -07:00
vagrant Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
virtualbox Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
vlc Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
zeromq Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07: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
local-setup-vars.yaml Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
local-setup.yaml Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
PLANS.md Made a lot of progress on automation. Created quite a few playbooks and thought about how to implement them most effectively! I'm going to work on installation scripts for ansible (so you could easily install it on a local or remote workstation), documentation, abstraction, and DRY principles etc. 2013-04-14 01:42:22 -07:00
README.md Reorganized current play books and added a new one, bottle-mongodb. 2013-04-12 01:08:24 -07:00
Vagrantfile Reorganized current play books and added a new one, bottle-mongodb. 2013-04-12 01:08:24 -07:00

Ansible Playbooks

Configure servers in a snap with these concise Ansible playbooks!

Current Playbooks:

  • ZeroMQ - open source high-performance asynchronous messaging library
  • Bottle-MongoDB - open source lightweight webserver/application and document-oriented database combination

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
  • PHP - 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.