dashboard/docs/getting-set-up.md - Issue 2701113002: Migrate to the Google Cloud SDK.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: dashboard/docs/getting-set-up.md

Issue 2701113002: Migrate to the Google Cloud SDK. (Closed)

Patch Set: Work for both old and new SDKs. Created 3 years, 10 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

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..a050ca7880248e50a5cb4a488e956c37f4f2986b 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

@@ -24,14 +21,16 @@ 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

-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

-owner permissions for the App Engine project; otherwise if you want to

-request to set a new default version for chromeperf.appspot.com you can

-contact chrome-perf-dashboard-team@google.com.

+To deploy, you can run `bin/deploy`, which prepares the code to be deployed and

+runs `gcloud app deploy`. If you modify any `*.yaml` files, you can pass them as

+parameters to `bin/deploy` to deploy the updated configs.

+When deploying services, `bin/deploy` 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 owner

+permissions for the App Engine project; otherwise if you want to request to set

+a new default version for chromeperf.appspot.com you can contact

+chrome-perf-dashboard-team@google.com.

After deploying, there is a checklist to verify that no major functionality

has regressed: [deploy checklist](/dashboard/docs/deploy-checklist.md).

« no previous file with comments | « dashboard/dashboard/__init__.py ('k') | dashboard/pinpoint.yaml » ('j') | no next file with comments »