|
16 | 16 | A live-update service for your NativeScript apps!
|
17 | 17 |
|
18 | 18 | <details>
|
19 |
| - <summary>*Optional reading: what this is, and how it works*</summary> |
| 19 | + <summary>Optional reading: what this is, and how it works</summary> |
20 | 20 |
|
21 | 21 | A NativeScript app is composed of XML/HTML, CSS and JavaScript files and any accompanying images, which are bundled together by the NativeScript CLI and distributed as part of a platform-specific binary (i.e. an .ipa or .apk file). Once the app is released, updating either the code (e.g. making bug fixes, adding new features) or image assets, requires you to recompile and redistribute the entire binary, which of course, includes any review time associated with the store(s) you are publishing to.
|
22 | 22 |
|
@@ -366,14 +366,16 @@ This won't roll back any releases, but it cleans up the history metadata (of the
|
366 | 366 | nativescript-code-push deployment clear <codepush-appname> Staging
|
367 | 367 | ```
|
368 | 368 |
|
369 |
| -## Testing CodePush packages during development |
| 369 | +## Advanced topics |
| 370 | + |
| 371 | +### Testing CodePush packages during development |
370 | 372 | You may want to play with CodePush before using it in production (smart move!).
|
371 | 373 | Perform these steps once you've pushed an update and added the `sync` command to your app:
|
372 | 374 |
|
373 | 375 | - `$ tns run <platform>`. On an iOS *device* add the `--release` flag so LiveSync doesn't interfere.
|
374 | 376 | - kill and restart the app after the update is installed
|
375 | 377 |
|
376 |
| -## Patching Update Metadata |
| 378 | +### Patching Update Metadata |
377 | 379 | After releasing an update, there may be scenarios where you need to modify one or more of the metadata attributes associated with it
|
378 | 380 | (e.g. you forgot to mark a critical bug fix as mandatory.
|
379 | 381 |
|
@@ -405,7 +407,7 @@ nativescript-code-push patch MyAppiOS Staging -t "1.0.0 - 1.0.5"
|
405 | 407 |
|
406 | 408 | </details>
|
407 | 409 |
|
408 |
| -## Promoting Updates |
| 410 | +### Promoting Updates |
409 | 411 | <details>
|
410 | 412 | <summary>Read this if you want to easily promote releases from Staging to Production</summary>
|
411 | 413 |
|
@@ -435,7 +437,7 @@ While you could use the `release` command to "manually" migrate an update from o
|
435 | 437 |
|
436 | 438 | </details>
|
437 | 439 |
|
438 |
| -## Rolling Back Updates |
| 440 | +### Rolling Back Updates |
439 | 441 |
|
440 | 442 | <details>
|
441 | 443 | <summary>Read this if you want to learn all about rollbacks</summary>
|
@@ -481,7 +483,7 @@ nativescript-code-push rollback MyAppiOS Production --targetRelease v34
|
481 | 483 |
|
482 | 484 | </details>
|
483 | 485 |
|
484 |
| -## App Collaboration |
| 486 | +### App Collaboration |
485 | 487 | <details>
|
486 | 488 | <summary>Working on one app with multiple developers? Click here!</summary>
|
487 | 489 |
|
@@ -520,7 +522,7 @@ nativescript-code-push collaborator ls <appName>
|
520 | 522 |
|
521 | 523 | </details>
|
522 | 524 |
|
523 |
| -## Using CodePush behind a proxy |
| 525 | +### Using CodePush behind a proxy |
524 | 526 | <details>
|
525 | 527 | <summary>Click here to read all about Proxy Support</summary>
|
526 | 528 | By default, the `login` command will automatically look for a system-wide proxy, specified via an `HTTPS_PROXY` or `HTTP_PROXY` environment variable, and use that to connect to the server.
|
|
0 commit comments