Closed patcon closed 11 years ago
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.
We should have a way to parse the repo key from config.yml
to get the organization and repo name. Working on that.
I think this is done satisfactorily :)
Beginning assumptions:
Potential rake tasks:
configure
: creates/modifies config.ymlcreate_server
: spins up fresh Rackspace serverprovision_jenkins
: runs chef on a new or established server for creation/update.setup_dns
: creates a new subdomain forci.PROJECT.example.com
for your DNS zone.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.service_hook
: sets up the project repo's service hook to point to the jenkins domain for triggering builds.deploy_key
: sends jenkins deploy key to github for attachment to project repo.create_repo
: forks drupal-skeletor and names it appropriately. (??)Not possible with current Dynect API.admin:prepare_dns_user
: Using master dynect API key, create a node for the project (ie.project.example.com
for theexample.com
zone), and provision a less-privileged dynect user that will be assigned to the team to manage their own DNS entries.