Skip to content

Commit b7482e3

Browse files
authored
Update addon_testing.markdown
1 parent 909d1a8 commit b7482e3

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

source/hassio/addon_testing.markdown

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,18 @@ The fastest way to develop add-ons is by adding them to your local add-on reposi
1313

1414
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.
1515

16+
## {% linkable_title Local run %}
17+
18+
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:
19+
- armhf: `resin/armhf-alpine:3.5`
20+
- aarch64: `resin/aarch64-alpine:3.5`
21+
- amd64: `resin/amd64-alpine:3.5`
22+
- i386: `resin/i386-alpine:3.5`
23+
24+
Use docker to build the test addon: `docker build -t local/my-test-addon .`
25+
26+
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`
27+
1628
## {% linkable_title Logs %}
1729

1830
All stdout and stderr is redirected to the Docker logs. The logs can be fetched from the add-on page inside the Hass.io panel in Home Assistant.

0 commit comments

Comments
 (0)