4 ms·

I was curious about that as well, especially given the latest cap news from the developer.

• yeukhon 13y ago
  I was more interested in why use it alongside with ansible; does it need to be multi-server automation? I thought it was just a toy server for development purpose. ansible seems enough for that kind of job (if it just needs to be a single server - and even for a few additional one that's adequate too.
  • ericclemmons 13y ago
    Ansible is actually provisioning our 3 different deployment environments: $ cd provisioning $ ansible-playbook provision -i local $ ansible-playbook provision -i staging $ ansible-playbook provision -i production Running `cap {env} genesis:provision` pretty much just runs that script, but has a fail-safe wrapper for the first time you provision a new server, because you will need to provide a username+password. After provisioning, there's a "deploy" user with a private key used for SSH going forward. Granted, I've only been using Ansible for about a week, but it is definitely better than the bash scripts used before :)
• ericclemmons 13y ago
  The news came after we already had all of this working for the past month. Now there's even more reason to replace it :)