mirror of
https://github.com/home-assistant/supervisor.git
synced 2025-04-19 10:47:15 +00:00
26024053ed
* Fix add-on store repository getting removed without internet Currently, when a git command error happens in `pull()`, we declare the repository as corrupt. Subsequent system autofix runs then execute the reset resolution, which essentially removes the git repository from the system. In situations where the Internet fails right between the last Supervisor connectivity check and the add-on store repository update (the connectivity checks are throttled to once every 10 minutes while connectivity is considered good), or if the outage is only partial (e.g. reaching connectivity check works but the store repository is not reachable), this leads to a git command error which declares the repository as corrupt just as well, and ultimately leads to the removal of the add-on store repository from the local system. Run a git ls-remote first, which is used as an extra connectivity check. This will also avoid removing the repository if Internet connectivity works but the git provider is temporary down or not reachable. That said, it will also fail if the repository is no longer present. But this case needs extra handling anyways. * Run git ls-remote in executor
Home Assistant Supervisor
First private cloud solution for home automation
Home Assistant (former Hass.io) is a container-based system for managing your Home Assistant Core installation and related applications. The system is controlled via Home Assistant which communicates with the Supervisor. The Supervisor provides an API to manage the installation. This includes changing network settings or installing and updating software.
Installation
Installation instructions can be found at https://home-assistant.io/getting-started.
Development
For small changes and bugfixes you can just follow this, but for significant changes open a RFC first. Development instructions can be found here.
Release
Releases are done in 3 stages (channels) with this structure:
- Pull requests are merged to the
mainbranch. - A new build is pushed to the
devstage. - Releases are published.
- A new build is pushed to the
betastage. - The
stable.jsonfile is updated. - The build that was pushed to
betawill now be pushed tostable.
