chromium/src
0
Fork 0
Code Activity

Add link to a tutorial to updater design_doc.md

Browse Source 
Change-Id: I4f7d9f65ce26e1ed0f0eda293833f76b36e1039a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5913512
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1364983}
This commit is contained in:
Michael Herrmann
2024-10-07 16:34:36 +00:00
committed by Chromium LUCI CQ
parent f8f3c9483f
commit 72cdc53a2a
2 changed files with 7 additions and 0 deletions

1
AUTHORS

@ -972,6 +972,7 @@ Michael Cirone <mikecirone@gmail.com>
Michael Constant <mconst@gmail.com>
Michael Forney <mforney@mforney.org>
Michael Gilbert <floppymaster@gmail.com>
Michael Herrmann <michael@herrmann.io>
Michael Kolomeytsev <michael.kolomeytsev@gmail.com>
Michael Lopez <lopes92290@gmail.com>
Michael Morrison <codebythepound@gmail.com>

6
docs/updater/design_doc.md

@ -35,6 +35,12 @@ communicating the state of installed applications, and receiving update
instructions. It applies updates the server instructs it to, and then reports
the results of the operation back to Omaha servers.
There is an [unofficial tutorial](https://omaha-consulting.com/chromium-updater-omaha-4-tutorial)
that gives a quick working overview of the updater. (Please note that it was
written by a third party, so its availability, accuracy and safety cannot be
guaranteed.)
## Updater Design
Once installed, the updater operates as a collection of processes that are
launched on-demand and orchestrate their operations over IPC. The *server