Chromium Code Reviews Chromium Code Reviews
Issue 2985493002:
config_service: README update (Closed)
| OLD | NEW |
|---|---|
| 1 # \<Config UI\> | 1 # LUCI Config UI |
| 2 | 2 |
| 3 This is a UI for the configuration service | 3 This is a UI for the configuration service. |
| 4 | 4 |
| 5 ## Install the Polymer-CLI | |
| 6 | 5 |
| 7 First, make sure you have the [Polymer CLI](https://www.npmjs.com/package/polyme r-cli) installed. Then run `polymer serve` to serve your application locally. | 6 ## Setting up |
| 8 | 7 |
| 9 ## Viewing Your Application | 8 *» First, make sure you have the [Polymer CLI](https://www.polymer-project. org/2.0/docs/tools/polymer-cli) installed. |
| 10 | 9 |
| 11 ``` | 10 * Install [Google App Engine SDK](https://cloud.google.com/appengine/downloads ). |
| 12 $ polymer serve | |
| 13 ``` | |
| 14 | 11 |
| 15 ## Building Your Application | 12 *» Run `bower install` in the ui directory to make sure you have all the de pendecies installed. |
|
Sergey Berezin
2017/07/19 23:05:10
dependencies (spelling)
| |
| 16 | 13 |
| 17 ``` | |
| 18 $ polymer build | |
| 19 ``` | |
| 20 | 14 |
| 21 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 `po lymer serve` a folder to serve from: | 15 ## Running locally |
| 22 | 16 |
| 23 ``` | 17 *» First, change all the URLs in the iron-ajax elements. Simply add "https: //luci-config.appspot.com" before each URL. |
| 24 $ polymer serve build/default | 18 » *» One in the src/config-ui/front-page.html |
| 25 ``` | 19 » *» Two in the src/config-ui/config-set.html |
| 20 | |
| 21 *» In the config-service folder run `dev_appserver.py app.yaml` | |
| 22 | |
| 23 *» Visit [http://localhost:8080](http://localhost:8080) | |
| 24 | |
| 26 | 25 |
| 27 ## Running Tests | 26 ## Running Tests |
| 28 | 27 |
| 29 ``` | 28 *» Your application is already set up to be tested via [web-component-teste r](https://github.com/Polymer/web-component-tester). |
| 30 $ polymer test | 29 » Run 'wct, 'wct -p' or 'polymer test' inside ui folder to run your applic ation's test suites locally. |
|
Sergey Berezin
2017/07/19 23:05:10
`wct` (backtick, and missing the closing one)
`wct
| |
| 31 ``` | 30 » These commands will run tests for all browsers installed on your compute r. |
| 32 | |
| 33 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 appl ication's test suite locally. | |
| 34 | 31 |
| 35 ## Third Party Files | 32 ## Third Party Files |
| 36 | 33 |
| 37 In order to use proper authentication, the google-signin-aware element was neede d. However, this element has not been updated to Polymer 2.0, so edits were made to the current version to ensure compatibility. | 34 In order to use proper authentication, the google-signin-aware element was neede d. However, this element has not been updated to |
| 35 Polymer 2.0, so edits were made to the current version to ensure compatibility. | |
| 38 The modified google-signin-aware element can be found in the ui/common/third_par ty/google-signin folder. | 36 The modified google-signin-aware element can be found in the ui/common/third_par ty/google-signin folder. |
| OLD | NEW |
