aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar Steren <steren.giannini@gmail.com>2017-01-03 18:43:18 +0000
committerGravatar John Cater <jcater@google.com>2017-01-03 20:49:37 +0000
commite86afd932c8e7cd024eecce74fcf6bece3623b02 (patch)
tree3df80fcd45b176cccc05eca7366c5a070f116ca9 /site
parent7a14ed00a20a7219be60e054c4d22bcf202df1c9 (diff)
Doc: Update wording for local run and 'Google Cloud Console' name
* The official App Engine docs do not use the term "deploy" when running the app locally (https://cloud.google.com/appengine/docs/java/tools/devserver). It's better to only use the word "deploy" when deploying to App Engine. * The Console where users can setup App Engine is the Google Cloud Console (https://console.cloud.google.com), not the Developer Console Closes #2329. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2329 PiperOrigin-RevId: 143460661 MOS_MIGRATED_REVID=143460661
Diffstat (limited to 'site')
-rw-r--r--site/versions/master/docs/tutorial/backend-server.md22
1 files changed, 13 insertions, 9 deletions
diff --git a/site/versions/master/docs/tutorial/backend-server.md b/site/versions/master/docs/tutorial/backend-server.md
index 45c6463077..137a97ab14 100644
--- a/site/versions/master/docs/tutorial/backend-server.md
+++ b/site/versions/master/docs/tutorial/backend-server.md
@@ -16,7 +16,7 @@ Here, you'll do the following:
* Create a `BUILD` file
* Run the build
* Find the build outputs
-* Deploy to a local development server
+* Run the application on a local development server
* Deploy to Google App Engine
Bazel provides a set of [App Engine build rules](/docs/be/appengine.html)
@@ -182,26 +182,30 @@ INFO: Elapsed time: 56.867s, Critical Path: 2.72s
The `.war` file and other outputs are located in the
`$WORKSPACE/bazel-bin/backend` directory.
-## Deploy to a local development server
+In particular, the `appengine_war` rule generates scripts that you can use to
+run your backend locally or deploy it to Google App Engine:
-The `appengine_war` rule generates an upload script that you can use to deploy
-your backend server on Google App Engine. Here, you'll start a local App Engine
-development server in your environment and deploy your application there.
+## Run the application on a local development server
-To deploy the application, enter the following:
+Here, you'll start a local App Engine development server in your environment and
+run your application on it.
+
+To run the application, enter the following:
```bash
$ bazel-bin/backend/backend --port=12345
```
-Your application URL will be `http://localhost:12345`
+Your application will be available at `http://localhost:12345`
## Deploy to Google App Engine
You can also deploy the application to the live App Engine serving
environment on Google Cloud Platform. For this scenario, you must first create
-a project in the
-[Google Developers Console](https://console.developers.google.com).
+a new Cloud Platform project and App Engine application using the Google Cloud
+Platform Console.
+Follow [this link](https://console.cloud.google.com/projectselector/appengine/create?lang=java&st=true)
+to perform these actions.
To deploy the application, enter the following: