|Hacker News, Reddit, Stack Overflow Stats|
|Description||Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine||Build, destroy and rebuild servers on any public or private cloud||A remote server automation and deployment tool written in Ruby|
|Why people like using this service||
|Companies using this service|
Ansible is used in both the development and production deployment process. A playbook couple with a Vagrantfile, easy deploys a local virtual machine that will mirror the setup in production.
ansible scripts in common deployment repo
playbooks with different roles
different env config properties in YAML file
After considering and experimenting with various other deployment tools and strategies, we have settled with Ansible for provisioning our servers. Our Ansible playbooks are reasonably high-level and concise, while still allowing for fine control where needed.
some deployment configuration and provisioning vagrant like in deployment
Ansible is the deployment tool for people who don't like deployment tools. It's close to scripting, doesn't pollute your servers with agents or centralized servers, and just makes immediate sense. The entire stack at Cloudcraft.co is orchestrated by Ansible. What does that mean? Beyond the obvious of installing packages and configuring services, Ansible coordinates all the machines into a working deployment: It adds API servers to the loadbancer pool, opens ports on the DB server for the backend servers to connect, gracefully upgrades services in a rolling fashion for zero-downtime deployments etc. And it's so easy to use, it's easier to use than doing things by hand, meaning it's a deployment tool you'll actually use every time!
All of our servers are provisioned by Ansible, with no manual provisioning involved. This lets us easily roll out new servers, with no chance for human error when configuring the servers. We use the same code to provision local development environments on Vagrant, which eliminates configuration discrepancies between development and production.
Provisioning and code deploys for our stack. Local dev workstations, staging, and production.
Out custom recipes makes it simple for developers bootstrap process (using vagrant) and that same recipe is also the one that is used to prep instances
Deployment automation all of the websites and apps are deployed to linux via capistrano.