diff options
| author | Jon Oster <jon.oster@here.com> | 2018-01-18 10:40:32 +0100 |
|---|---|---|
| committer | Jon Oster <jon.oster@here.com> | 2018-01-18 12:32:57 +0100 |
| commit | 10ae4092dc80e598f996a9ec06148117b7db6dc9 (patch) | |
| tree | 6aff090fc39ea20f910c323470d9323f5c2145f9 | |
| parent | 0afff0c944763238026283fbb409d038705c6b13 (diff) | |
| download | meta-updater-10ae4092dc80e598f996a9ec06148117b7db6dc9.tar.gz | |
PRO-4645 Update OSTree httpd instructions
| -rw-r--r-- | README.adoc | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/README.adoc b/README.adoc index 0917e45..e82b904 100644 --- a/README.adoc +++ b/README.adoc | |||
| @@ -79,25 +79,25 @@ Although we have used U-Boot so far, other boot loaders can be configured work w | |||
| 79 | 79 | ||
| 80 | === OSTree | 80 | === OSTree |
| 81 | 81 | ||
| 82 | OSTree includes its own simple http server. It just exposes the whole OSTree repository to the network so that any remote device can pull data from it to device's local repository. To use the OSTree http server, you will need OSTree installed on your build machine. (Alternatively, you could run version built inside Yocto using bitbake's http://www.openembedded.org/wiki/Devshell[devshell].) | 82 | OSTree used to include a simple HTTP server as part of the ostree binary, but this has been removed in more recent versions. However, OSTree repositories are self-contained directories, and can be trivially served over the network using any HTTP server. For example, you could use Python's SimpleHTTPServer: |
| 83 | |||
| 84 | To expose your repo, run ostree trivial-httpd using any free port: | ||
| 85 | 83 | ||
| 86 | .... | 84 | .... |
| 87 | ostree trivial-httpd tmp/deploy/images/qemux86-64/ostree_repo -P 57556 | 85 | cd tmp/deploy/images/qemux86-64/ostree_repo |
| 86 | python -m SimpleHTTPServer <port> # port defaults to 8000 | ||
| 88 | .... | 87 | .... |
| 89 | 88 | ||
| 90 | You can then run ostree from inside your device by adding your repo: | 89 | You can then run ostree from inside your device by adding your repo: |
| 91 | 90 | ||
| 92 | .... | 91 | .... |
| 93 | # agl-remote identifies the remote server in your local repo | 92 | # This behaves like adding a Git remote; you can name it anything |
| 94 | ostree remote add --no-gpg-verify my-remote http://192.168.7.1:57556 ota | 93 | ostree remote add --no-gpg-verify my-remote http://<your-ip>:<port> |
| 95 | 94 | ||
| 96 | # ota is a branch name in the remote repo, set in OSTREE_BRANCHNAME | 95 | # If OSTREE_BRANCHNAME is set in local.conf, that will be the name of the |
| 97 | ostree pull my-remote ota | 96 | # branch. If not set, it defaults to the value of MACHINE (e.g. qemux86-64). |
| 97 | ostree pull my-remote <branch> | ||
| 98 | 98 | ||
| 99 | # poky is OS name as set in OSTREE_OSNAME | 99 | # poky is the OS name as set in OSTREE_OSNAME |
| 100 | ostree admin deploy --os=poky my-remote:ota | 100 | ostree admin deploy --os=poky my-remote:<branch> |
| 101 | .... | 101 | .... |
| 102 | 102 | ||
| 103 | After restarting, you will boot into the newly deployed OS image. | 103 | After restarting, you will boot into the newly deployed OS image. |