Update system

• What do Repo update flags mean?
• How to get files for creating a Unit?
• How to update a Unit?
• How does a Unit learn its current version using env.json?
• How are Unit update archives generated?
• What MQTT commands exist for updating a Unit?
• How does Pepeunit know the current version of a Unit?
• How do Units get links to compiled versions?

Process of updating all Units linked to a Repo

Manual

1. Update the local RepositoryRegisty via the Update Local Repository button.
2. Pepeunit forcibly replaces the local repository with the new one. The maximum update frequency is limited by the PU_MIN_INTERVAL_SYNC_REPOSITORY variable.

Updating related Unit

1. The Repo creator clicks the Update related Unit button in the Repo menu.
2. Pepeunit calls the MQTT command UPDATE - update/pepeunit for each Unit that has automatic updates enabled.

Automatic or by Administrator request

1. Every hour, or when the Administrator presses the Update all Repo and Unit button, an update task is started in the Domain entity of the Frontend to update all Unit instances in accordance with the current state of physical RepositoryRegisty.
2. Pepeunit selects Repo objects that have automatic updates enabled.
3. Pepeunit calls the MQTT command UPDATE - update/pepeunit for each Unit that has automatic updates enabled.

WARNING

To improve performance, updates of Unit and RepositoryRegisty are desynchronized by half an hour.

Algorithm for calculating the current Unit version