summaryrefslogtreecommitdiff
path: root/posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md (renamed from content/post/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md)6
1 files changed, 0 insertions, 6 deletions
diff --git a/content/post/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md b/posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md
index f311d3e..416cac7 100644
--- a/content/post/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md
+++ b/posts/2014-02-01-provision-an-ec2-instance-with-vagrant-and-ansible.md
@@ -1,9 +1,3 @@
----
-date: 2014-02-01T00:00:00Z
-summary: In which I provision an EC2 instance with Vagrant and Ansible
-title: Provisioning an EC2 instance with Vagrant and Ansible
----
-
I like to use [Ansible](http://www.ansible.com/) to manage my personal servers. It forces me to make the environment reproducible so I don't have to care about a specific box: I can throw them away easily, knowing I can get a new one when I need, with the exact same configuration.
I also find Ansible easier to reason about than Chef or Puppet. The fact that I have to manage and maintain only a few machines is probably why.