From 78f201046b89655fcf03179ec59ff3349e618682 Mon Sep 17 00:00:00 2001
From: Lloyd Hilaiel <lloyd@hilaiel.com>
Date: Thu, 7 Jun 2012 13:44:00 +0300
Subject: [PATCH] make aws deployment consistent, referring to vm as
'some_name_i_chose' in section describing how to tear down VMs
---
docs/AWS_DEPLOYMENT.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/AWS_DEPLOYMENT.md b/docs/AWS_DEPLOYMENT.md
index 92f3a4ccc..5d31edb28 100644
--- a/docs/AWS_DEPLOYMENT.md
+++ b/docs/AWS_DEPLOYMENT.md
@@ -137,12 +137,12 @@ You are pushing *from* the local `myotherbranch`, to the remote `master`.
These things cost money by the hour, not a lot, but money. So when you want to
decommission a VM and release your hold on the DNS name, simply:
- $ scripts/deploy.js destroy awstest
- awsbox cmd: node_modules/.bin/awsbox destroy awstest
- trying to destroy VM for awstest: done
+ $ scripts/deploy.js destroy some_name_i_chose
+ awsbox cmd: node_modules/.bin/awsbox destroy some_name_i_chose
+ trying to destroy VM for some_name_i_chose: done
trying to remove git remote: done
- trying to remove DNS: awstest.personatest.org
- deleting awstest.personatest.org: done
+ trying to remove DNS: some_name_i_chose.personatest.org
+ deleting some_name_i_chose.personatest.org: done
## Overview of what's deployed to VMs
--
GitLab