jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-22 00:36:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Use same product name

Browse Source
This commit is contained in:
Fabian Affolter 2017-05-09 20:15:04 +02:00
parent 24370fabb2
commit 4ae27c0f80
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
3 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/hassio/addon_development.markdown
View File

@ -11,4 +11,4 @@ footer: true
Add-ons for Hass.io allows the user to extend the functionality around Home Assistant. This can be running an application that Home Assistant can integrate with (like an MQTT broker) or to share the configuration via Samba for easy editing from other computers. Add-ons can be configured via the Hass.io panel in Home Assistant.
Under the hood, add-ons are Docker images published in [Docker hub](https://hub.docker.com/). Developers can create [GitHub](https://github.com) repositories that contain multiple references to add-ons for easy sharing with the community.
Under the hood, add-ons are Docker images published in [Docker Hub](https://hub.docker.com/). Developers can create [GitHub](https://github.com) repositories that contain multiple references to add-ons for easy sharing with the community.

6
source/hassio/addon_publishing.markdown
View File

@ -9,7 +9,7 @@ sharing: true
footer: true
---
All add-ons are simple docker containers. You can use our [build scripts][builder] to automate the whole build process or you can build your own docker image and push it manually to a docker hub. Inside your addon `config.json` you specify the Docker image that will be installed for your add-on:
All add-ons are simple docker containers. You can use our [build scripts][builder] to automate the whole build process or you can build your own docker image and push it manually to a docker hub. Inside your add-on `config.json` you specify the Docker image that will be installed for your add-on:
```json
{
@ -19,11 +19,11 @@ All add-ons are simple docker containers. You can use our [build scripts][builde
You can use `{arch}` inside the image name to support multiple architectures with 1 configuration file. It will be replaced with the architecture of the user when we load the image.
Development best practices is to merge your changes into a branch like `build`. After you push the addon to docker hub, you can merge this branch to master.
Development best practices is to merge your changes into a branch like `build`. After you push the add-on to [Docker Hub](https://hub.docker.com/), you can merge this branch to master.
## {% linkable_title Custom Add-ons %}
You need a docker hub account to make your own add-ons. Download our [build script][builder] and run one of the following commands.
You need a Docker Hub account to make your own add-ons. Download our [build script][builder] and run one of the following commands.
For a git repository:

9
source/hassio/addon_testing.markdown
View File

@ -11,19 +11,20 @@ footer: true
The fastest way to develop add-ons is by adding them to your local add-on repository. To access your local add-on repository, install either the [Samba add-on] or [SSH add-on].
Right now add-ons will only work with images that are stored on Dockerhub (using `image` from add-on config). We're working on enabling local add-ons to be built on the device.
Right now add-ons will only work with images that are stored on Docker Hub (using `image` from add-on config). We're working on enabling local add-ons to be built on the device.
## {% linkable_title Local run %}
You can build an try the addon on your developer machine also. Move all addon stuff into a temp folder. Replace on Dockerfile: `%%VERSION%%` with your version and `%%BASE_IMAGE%%` with:
You can build an try the addon on your developer machine also. Move all addon stuff into a temp folder. Replace in the Dockerfile: `%%VERSION%%` with your version and `%%BASE_IMAGE%%` with:
- armhf: `resin/armhf-alpine:3.5`
- aarch64: `resin/aarch64-alpine:3.5`
- amd64: `resin/amd64-alpine:3.5`
- i386: `resin/i386-alpine:3.5`
Use docker to build the test addon: `docker build -t local/my-test-addon .`
Use `docker` to build the test addon: `docker build -t local/my-test-addon .`
Create a new folder for data and add a test _options.json_. After that you can run our addon with: `docker run --rm -v /tmp/my_test_data:/data -p PORT_STUFF_IF_NEEDED local/my-test-addon`
Create a new folder for data and add a test _options.json_ file. After that you can run your add-on with: `docker run --rm -v /tmp/my_test_data:/data -p PORT_STUFF_IF_NEEDED local/my-test-addon`
## {% linkable_title Logs %}