mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 15:26:59 +00:00
Update addon_config.markdown
This commit is contained in:
parent
f147350ab4
commit
ffb528dbd6
@ -112,7 +112,7 @@ The config for an add-on is stored in `config.json`.
|
|||||||
| version | string | yes | Version of the add-on
|
| version | string | yes | Version of the add-on
|
||||||
| slug | string | yes | Slug of the add-on
|
| slug | string | yes | Slug of the add-on
|
||||||
| description | string | yes | Description of the add-on
|
| description | string | yes | Description of the add-on
|
||||||
| arch | array | no | List of supported arch: `armhf`, `aarch64`, `amd64`, `i386`. Default all.
|
| arch | list | no | List of supported arch: `armhf`, `aarch64`, `amd64`, `i386`. Default all.
|
||||||
| url | url | no | Homepage of the addon. Here you can explain the add-ons and options.
|
| url | url | no | Homepage of the addon. Here you can explain the add-ons and options.
|
||||||
| startup | bool | yes | `initialize` will start addon on setup of Hass.io. `system` is for things like databases and not dependent on other things. `services` will start before Home Assistant, while `application` is started afterwards. Finally `once` is for applications that don't run as a daemon.
|
| startup | bool | yes | `initialize` will start addon on setup of Hass.io. `system` is for things like databases and not dependent on other things. `services` will start before Home Assistant, while `application` is started afterwards. Finally `once` is for applications that don't run as a daemon.
|
||||||
| webui | string | no | A URL for web interface of this add-on. Like `http://[HOST]:[PORT:2839]/dashboard`, the port needs the internal port, which will be replaced with the effective port. It is also possible to bind the proto part to a config options with: `[PROTO:option_name]://[HOST]:[PORT:2839]/dashboard` and he lookup if they is True and going to `https`.
|
| webui | string | no | A URL for web interface of this add-on. Like `http://[HOST]:[PORT:2839]/dashboard`, the port needs the internal port, which will be replaced with the effective port. It is also possible to bind the proto part to a config options with: `[PROTO:option_name]://[HOST]:[PORT:2839]/dashboard` and he lookup if they is True and going to `https`.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user