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-16 05:46:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update addon_publishing.markdown

Browse Source
This commit is contained in:
Paulus Schoutsen 2017-05-07 09:15:23 -07:00 committed by GitHub
parent 4880c60f5d
commit 5dfc00d68c
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
source/hassio/addon_publishing.markdown
View File

@ -9,30 +9,29 @@ sharing: true
footer: true footer: true
--- ---
At the end, all add-ons are simple docker container. You can use our [build scripts][builder] for automate the hole process our you can build your own docker image and push it manual do a docker hub. Inside your addon `config.json` can you use: At the end, all add-ons are simple docker container. You can use our [build scripts][builder] that automate the whole 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:
```json ```json
{
"image": "myhub/image-addon-name"
}
{ {
"image": "myhub/image-{arch}-addon-name" "image": "myhub/image-{arch}-addon-name"
} }
``` ```
To specify from where it will load the addon by user installation. With `{arch}` inside image name, you can build your addon for multible architectures. 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.
Best praxis is to merge change 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 addon to docker hub, you can merge this branch to master.
## {% linkable_title Custom Add-ons %} ## {% linkable_title Custom Add-ons %}
You need a docker hub account. It is also possible to use our own docker registrator. Download our [build script][builder] local. You need a docker hub account to make your own add-ons. Download our [build script][builder] local.
For a git repository: For a git repository:
```bash ```bash
# Test only: # Test only:
./create_hassio_addon.sh -a amd64 -s addon-slug -r https://github.com/xy/addons -b branchname ./create_hassio_addon.sh -a amd64 -s addon-slug -r https://github.com/xy/addons -b branchname
# push do docker hub: # push to docker hub:
./create_hassio_addon.sh -a amd64 -s addon-slug -r https://github.com/xy/addons -b branchname -p ./create_hassio_addon.sh -a amd64 -s addon-slug -r https://github.com/xy/addons -b branchname -p
# create for all supported arch: # create for all supported arch:
@ -40,11 +39,12 @@ For a git repository:
``` ```
For a local repository: For a local repository:
```bash ```bash
# Test only: # Test only:
./create_hassio_addon.sh -a amd64 -s addon-slug -l /home/xy/my_local_repo ./create_hassio_addon.sh -a amd64 -s addon-slug -l /home/xy/my_local_repo
# push do docker hub: # push to docker hub:
./create_hassio_addon.sh -a amd64 -s addon-slug -l /home/xy/my_local_repo -p ./create_hassio_addon.sh -a amd64 -s addon-slug -l /home/xy/my_local_repo -p
``` ```