Update addon_publishing.markdown
This commit is contained in:
parent
f3fc73c6e8
commit
48b49f7047
1 changed files with 18 additions and 1 deletions
|
@ -9,4 +9,21 @@ sharing: true
|
||||||
footer: true
|
footer: true
|
||||||
---
|
---
|
||||||
|
|
||||||
[placeholder]
|
At the end, all add-ons are simple docker container. You can use our build scripts 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:
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"image": "myhub/image-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.
|
||||||
|
|
||||||
|
|
||||||
|
## {% linkable_title Custom Add-ons %}
|
||||||
|
|
||||||
|
You need a docker hub account. It is also possible to use our own docker registrator.
|
||||||
|
|
||||||
|
## {% linkable_title Core Add-ons %}
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue