From 755b2033febd8587b29e7b0a48ec4e976325f871 Mon Sep 17 00:00:00 2001
From: Fabio Rehm <fgrehm@gmail.com>
Date: Sat, 9 Mar 2013 16:11:49 -0300
Subject: [PATCH] Remove .dev from Vagrantfiles file names

---
 README.md                                              | 7 ++-----
 development/{Vagrantfile.dev.lxc => Vagrantfile.lxc}   | 0
 development/{Vagrantfile.dev.vb => Vagrantfile.vb.1.0} | 0
 3 files changed, 2 insertions(+), 5 deletions(-)
 rename development/{Vagrantfile.dev.lxc => Vagrantfile.lxc} (100%)
 rename development/{Vagrantfile.dev.vb => Vagrantfile.vb.1.0} (100%)

diff --git a/README.md b/README.md
index f5467d2..b4baac2 100644
--- a/README.md
+++ b/README.md
@@ -126,7 +126,7 @@ ready for development:
 ```sh
 bundle install
 cd development
-cp Vagrantfile.dev.lxc Vagrantfile
+cp Vagrantfile.lxc Vagrantfile
 # Required in order to allow nested containers to be started
 sudo apt-get install apparmor-utils && sudo aa-complain /usr/bin/lxc-start
 ./setup-lxc-dev-box
@@ -143,7 +143,7 @@ start nested containers there to try things out.
 
 ```
 cd development
-cp Vagrantfile.dev.vb Vagrantfile
+cp Vagrantfile.vb.1.0 Vagrantfile
 vagrant up
 ```
 
@@ -161,9 +161,6 @@ LXC_START_LOG_FILE=/tmp/lxc-start.log VAGRANT_LOG=debug vagrant-lxc up
 This will output A LOT of information on your terminal and some useful information
 about `lxc-start` to `/tmp/lxc-start.log`.
 
-Debugging whats going on with the container itself is a pain, there are some
-nice little scripts on the [/dev](dev) folder of the project.
-
 
 ## Help!
 
diff --git a/development/Vagrantfile.dev.lxc b/development/Vagrantfile.lxc
similarity index 100%
rename from development/Vagrantfile.dev.lxc
rename to development/Vagrantfile.lxc
diff --git a/development/Vagrantfile.dev.vb b/development/Vagrantfile.vb.1.0
similarity index 100%
rename from development/Vagrantfile.dev.vb
rename to development/Vagrantfile.vb.1.0