Streamline project launch so that anyone can set it up with helper scripts

[patcon]

Beginning assumptions:

• Rackspace servers will be used
• DynDNS will be used for DNS records
• Github used to host project

Potential rake tasks:

• [x] configure: creates/modifies config.yml
• [x] create_server: spins up fresh Rackspace server
• [x] provision_jenkins: runs chef on a new or established server for creation/update.
• [x] setup_dns: creates a new subdomain for ci.PROJECT.example.com for your DNS zone.
• [x] generate_users: creates the appropriate user files from a github team, which will be used to give everyone on the team ssh and jenkins login access.
• [x] service_hook: sets up the project repo's service hook to point to the jenkins domain for triggering builds.
• [x] deploy_key: sends jenkins deploy key to github for attachment to project repo.
• [x] create_repo: forks drupal-skeletor and names it appropriately. (??)
• [ ] admin:prepare_dns_user: Using master dynect API key, create a node for the project (ie. project.example.com for the example.com zone), and provision a less-privileged dynect user that will be assigned to the team to manage their own DNS entries. Not possible with current Dynect API.
• [ ] Add master task that stitches all these together for ease.

[patcon]

Need to make it a more fluid process for a privilidged admin (with API keys for rackspace and dyndns) to spin up the server, then pass the ip and root password to a team member for them to continue the rest of the setup.

[patcon]

We should have a way to parse the repo key from config.yml to get the organization and repo name. Working on that.

[patcon]

I think this is done satisfactorily :)