File:Extension-packaging.png
Original file (2,592 × 2,688 pixels, file size: 656 KB, MIME type: image/png)
Summary
High-level diagram of the Packaging Service context. The Packaging service relies on release events published to a webhook by the Interactions service to learn of new releases, and downloads source code from the Root Registry to build binaries. For each binary package it builds, it publishes an event to the Interactions service.
For such events, the Interactions can call webhooks for downstream packagers such as apt, yum, pgxman, and trunk. These services can then download binaries from Packaging and bundle them into packages for their specific packaging systems and post links back to Interactions.
Alternatively, as modeled by dbdev a downstream packager might listen for webhook events for new releases (or rely on a feed), download source code from the Root Registry, and bundle extensions from source. They also can post links back to Interactions.
File history
Click on a date/time to view the file as it appeared at that time.
| Date/Time | Thumbnail | Dimensions | User | Comment | |
|---|---|---|---|---|---|
| current | 22:29, 15 May 2024 | | 2,592 × 2,688 (656 KB) | Theory (talk | contribs) | |
| 18:12, 22 April 2024 |  | 2,520 × 2,716 (676 KB) | Theory (talk | contribs) | High-level diagram of the Packaging Service context. The ''Packaging'' service relies on release events published to a webhook by the ''Interactions'' service to learn of new releases, and downloads source code from the ''Root Registry'' to build binaries. For each binary package it builds, it publishes an event to the ''Interactions'' service.<br/><br/> For such events, the ''Interactions'' can call webhooks for downstream packagers such as apt, yum, pgxman, and trunk. These services can the... |
You cannot overwrite this file.
File usage
The following page uses this file:
