Migrate to the Google Cloud SDK.

dashboard/docs/getting-set-up.md

Index: dashboard/docs/getting-set-up.md
diff --git a/dashboard/docs/getting-set-up.md b/dashboard/docs/getting-set-up.md
index 4ce4efedc9f9acdb24ee70f299f392e49968b6d3..1907671857af7d49a1e51b080921a4950edfca8d 100644
--- a/dashboard/docs/getting-set-up.md
+++ b/dashboard/docs/getting-set-up.md
@@ -2,11 +2,8 @@
 
 ## Prerequisites
 
-Running the tests, running the local server and
-deploying all depends on having the [the App Engine
-SDK](https://cloud.google.com/appengine/downloads).
-
-After downloading and unpacking, you should add the path to the SDK to `PATH`.
+Running the tests, running the local server, and deploying depend on having
+the [the Google Cloud SDK](https://cloud.google.com/sdk/downloads).
 
 ## Running the tests
 
@@ -25,7 +22,7 @@ To load sample graph or alert data from production, navigate to
 ## Deploying to production
 
 To deploy, you can run `bin/deploy`, which prepares the
-code to be deployed and runs `appcfg.py`. Note that this
+code to be deployed and runs `gcloud app deploy`. Note that this

[sullivan, 2017/02/20 14:58:36]

Isn't it now `gcloud app deploy <filename.yaml>`? Shouldn't this section also
explain the different yaml files and when you would want to deploy which?

[dtu, 2017/02/22 01:09:40]

Done. (`/bin/deploy` with no parameters deploys the default service.)

 doesn't set the new version as the default version; to do
 this, you can use the versions page on the [Google Developers
 Console](https://console.developers.google.com/) if you have edit or