mirror of https://github.com/home-assistant/supervisor.git synced 2026-04-27 02:42:42 +00:00

Go to file

Jan Čermák 2e22e1e884 Add endpoint for complete logs of the latest container startup (#6163 )

* Add endpoint for complete logs of the latest container startup

Add endpoint that returns complete logs of the latest startup of
container, which can be used for downloading Core logs in the frontend.

Realtime filtering header is used for the Journal API and StartedAt
parameter from the Docker API is used as the reference point. This means
that any other Range header is ignored for this parameter, yet the
"lines" query argument can be used to limit the number of lines. By
default "infinite" number of lines is returned.

Closes #6147

* Implement fallback for latest logs for OS older than 16.0

Implement fallback which uses the internal CONTAINER_LOG_EPOCH metadata
added to logs created by the Docker logger. Still prefer the time-based
method, as it has lower overhead and using public APIs.

* Address review comments

* Only use CONTAINER_LOG_EPOCH for latest logs

As pointed out in the review comments, we might not be able to get the
StartedAt for add-ons that are not running. Thus we need to use the only
reliable mechanism available now, which is the container log epoch.

* Remove dead code for 'Range: realtime' header handling

2025-09-16 11:29:28 +02:00

.devcontainer

Update Python to 3.13 (#5564 )

2025-01-21 11:57:30 +01:00

.github

Bump home-assistant/builder from 2025.03.0 to 2025.09.0 (#6190 )

2025-09-16 09:06:10 +02:00

.vscode

Migrate to Ruff for lint and format (#4852 )

2024-02-05 11:37:39 -05:00

rootfs/etc

Avoid empty newlines in Supervisor logs (#4698 )

2023-11-13 20:12:17 +01:00

script

Add mypy to ci and precommit (#5969 )

2025-06-24 11:48:03 +02:00

supervisor

Add endpoint for complete logs of the latest container startup (#6163 )

2025-09-16 11:29:28 +02:00

tests

Add endpoint for complete logs of the latest container startup (#6163 )

2025-09-16 11:29:28 +02:00

.dockerignore

Add Audio layer / PulseAudio (#1523 )

2020-02-25 18:37:06 +01:00

.gitignore

Storage space usage API (#6046 )

2025-08-19 10:54:53 +02:00

.ha-frontend-version

Update frontend to version 20250811.0 (#6091 )

2025-08-12 09:51:46 +02:00

.hadolint.yaml

Revert "Revert "Update base images to 3.11-alpine3.18 (#4639 )" (#4646 )" (#4657 )

2023-11-02 11:29:15 +01:00

.pre-commit-config.yaml

Add mypy to ci and precommit (#5969 )

2025-06-24 11:48:03 +02:00

.vcnignore

Sign code folder (#2725 )

2021-03-16 15:47:40 +01:00

build.yaml

Update to Alpine 3.22 (#6054 )

2025-08-04 09:50:27 +02:00

CLAUDE.md

Add GitHub Copilot/Claude instruction (#5986 )

2025-07-04 07:05:05 +02:00

codecov.yaml

Remove annotations (#2007 )

2020-09-03 16:36:09 +02:00

Dockerfile

Bump uv to 0.8.9 (#6097 )

2025-08-13 16:27:56 +02:00

LICENSE

Update LICENSE

2020-07-29 14:45:37 +02:00

MANIFEST.in

Add Audio layer / PulseAudio (#1523 )

2020-02-25 18:37:06 +01:00

pyproject.toml

Bump setuptools from 80.8.0 to 80.9.0 (#5919 )

2025-05-27 12:13:06 +02:00

README.md

Add OHF logo to README (#5316 )

2024-09-30 18:42:08 +02:00

requirements_tests.txt

Bump types-docker from 7.1.0.20250907 to 7.1.0.20250916 (#6191 )

2025-09-16 09:57:24 +02:00

requirements.txt

Bump sentry-sdk from 2.37.1 to 2.38.0 (#6192 )

2025-09-16 10:00:50 +02:00

setup.py

Use version which is treated CalVer by AwesomeVersion (#5572 )

2025-01-24 09:59:50 +01:00

tox.ini

Migrate to Ruff for lint and format (#4852 )

2024-02-05 11:37:39 -05:00

README.md

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 main branch.
A new build is pushed to the dev stage.
Releases are published.
A new build is pushed to the beta stage.
The stable.json file is updated.
The build that was pushed to beta will now be pushed to stable.