Chromium Code Reviews| Index: appengine/config_service/ui/README.md |
| diff --git a/appengine/config_service/ui/README.md b/appengine/config_service/ui/README.md |
| index c938e6be3f3e2944827b59b92bf6cb7fa26e208b..4d1261e323547a02c11bfad01b0c27059d0ee48f 100644 |
| --- a/appengine/config_service/ui/README.md |
| +++ b/appengine/config_service/ui/README.md |
| @@ -1,38 +1,36 @@ |
| -# \<Config UI\> |
| +# LUCI Config UI |
| -This is a UI for the configuration service |
| +This is a UI for the configuration service. |
| -## Install the Polymer-CLI |
| -First, make sure you have the [Polymer CLI](https://www.npmjs.com/package/polymer-cli) installed. Then run `polymer serve` to serve your application locally. |
| +## Setting up |
| -## Viewing Your Application |
| +* First, make sure you have the [Polymer CLI](https://www.polymer-project.org/2.0/docs/tools/polymer-cli) installed. |
| -``` |
| -$ polymer serve |
| -``` |
| +* Install [Google App Engine SDK](https://cloud.google.com/appengine/downloads). |
| -## Building Your Application |
| +* Run `bower install` in the ui directory to make sure you have all the dependecies installed. |
|
Sergey Berezin
2017/07/19 23:05:10
dependencies (spelling)
|
| -``` |
| -$ polymer build |
| -``` |
| -This will create builds of your application in the `build/` directory, optimized to be served in production. You can then serve the built versions by giving `polymer serve` a folder to serve from: |
| +## Running locally |
| -``` |
| -$ polymer serve build/default |
| -``` |
| +* First, change all the URLs in the iron-ajax elements. Simply add "https://luci-config.appspot.com" before each URL. |
| + * One in the src/config-ui/front-page.html |
| + * Two in the src/config-ui/config-set.html |
| -## Running Tests |
| +* In the config-service folder run `dev_appserver.py app.yaml` |
| + |
| +* Visit [http://localhost:8080](http://localhost:8080) |
| -``` |
| -$ polymer test |
| -``` |
| -Your application is already set up to be tested via [web-component-tester](https://github.com/Polymer/web-component-tester). Run `polymer test` to run your application's test suite locally. |
| +## Running Tests |
| + |
| +* Your application is already set up to be tested via [web-component-tester](https://github.com/Polymer/web-component-tester). |
| + Run 'wct, 'wct -p' or 'polymer test' inside ui folder to run your application's test suites locally. |
|
Sergey Berezin
2017/07/19 23:05:10
`wct` (backtick, and missing the closing one)
`wct
|
| + These commands will run tests for all browsers installed on your computer. |
| ## Third Party Files |
| -In order to use proper authentication, the google-signin-aware element was needed. However, this element has not been updated to Polymer 2.0, so edits were made to the current version to ensure compatibility. |
| +In order to use proper authentication, the google-signin-aware element was needed. However, this element has not been updated to |
| +Polymer 2.0, so edits were made to the current version to ensure compatibility. |
| The modified google-signin-aware element can be found in the ui/common/third_party/google-signin folder. |