| OLD | NEW |
| 1 # mojo_run | 1 # mojo_run |
| 2 | 2 |
| 3 `mojo_run` allows you to run a Mojo shell either on the host, or on an attached | 3 `mojo_run` allows you to run a Mojo shell either on the host, or on an attached |
| 4 Android device. | 4 Android device. |
| 5 | 5 |
| 6 ```sh | 6 ```sh |
| 7 mojo_run APP_URL # Run on the host. | 7 mojo_run APP_URL # Run on the host. |
| 8 mojo_run APP_URL --android # Run on Android device. | 8 mojo_run APP_URL --android # Run on Android device. |
| 9 mojo_run "APP_URL APP_ARGUMENTS" # Run an app with startup arguments | 9 mojo_run "APP_URL APP_ARGUMENTS" # Run an app with startup arguments |
| 10 ``` | 10 ``` |
| 11 | 11 |
| 12 Unless running within a Mojo checkout, we need to indicate the path to the shell | 12 Unless running within a Mojo checkout, we need to indicate the path to the shell |
| 13 binary: | 13 binary: |
| 14 | 14 |
| 15 ```sh | 15 ```sh |
| 16 mojo_run --shell-path path/to/shell/binary APP_URL | 16 mojo_run --shell-path path/to/shell/binary APP_URL |
| 17 ``` | 17 ``` |
| 18 | 18 |
| 19 Some applications are meant to be run embedded in a **window manager**. To run | 19 Some applications implement ViewProvider and are run embedded in a view. To run |
| 20 these, you can pass the app url using the `--embed` flag. This will run the | 20 these, you can pass the app url using the `--embed` flag: |
| 21 window manager and pass the given url to it: | |
| 22 | 21 |
| 23 ```sh | 22 ```sh |
| 24 mojo_run --embed APP_URL [--android] | 23 mojo_run --embed APP_URL [--android] |
| 25 ``` | 24 ``` |
| 26 | 25 |
| 27 By default, `mojo_run` uses mojo:kiosk_wm as the window manager. You can pass a | |
| 28 different window manager url using the `--window-manager` flag to override this. | |
| 29 | |
| 30 ## Running multiple instances simultaneously | 26 ## Running multiple instances simultaneously |
| 31 | 27 |
| 32 `mojo_run` sets up development servers on fixed ports to facilitate caching | 28 `mojo_run` sets up development servers on fixed ports to facilitate caching |
| 33 between runs and allow the script to work remotely using `adb_remote_setup`. | 29 between runs and allow the script to work remotely using `adb_remote_setup`. |
| 34 This would normally prevent two or more instances of `mojo_run` from running | 30 This would normally prevent two or more instances of `mojo_run` from running |
| 35 simulatenously as the development servers cannot be spawned twice on the same | 31 simulatenously as the development servers cannot be spawned twice on the same |
| 36 ports. | 32 ports. |
| 37 | 33 |
| 38 In order to run the same set of binaries simultaneously one can use the | 34 In order to run the same set of binaries simultaneously one can use the |
| 39 `--reuse-servers` switch for second and further instances. This will make the | 35 `--reuse-servers` switch for second and further instances. This will make the |
| (...skipping 31 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 71 ``` | 67 ``` |
| 72 | 68 |
| 73 ## Setting default mojo origin | 69 ## Setting default mojo origin |
| 74 | 70 |
| 75 When run outside of the `domokit/mojo` repository, `mojo_run` needs `--origin` | 71 When run outside of the `domokit/mojo` repository, `mojo_run` needs `--origin` |
| 76 parameter to indicate where binaries of the core mojo services come from. If a | 72 parameter to indicate where binaries of the core mojo services come from. If a |
| 77 `MOJO_VERSION` file is present among ancestors of `mojo_run` and `--origin` | 73 `MOJO_VERSION` file is present among ancestors of `mojo_run` and `--origin` |
| 78 parameter is not set, origin will point to Google Storage location storing | 74 parameter is not set, origin will point to Google Storage location storing |
| 79 binaries of core mojo services built at the git revision indicated in | 75 binaries of core mojo services built at the git revision indicated in |
| 80 `MOJO_VERSION`. | 76 `MOJO_VERSION`. |
| OLD | NEW |