You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/hassio/addon_testing.markdown
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,18 @@ The fastest way to develop add-ons is by adding them to your local add-on reposi
13
13
14
14
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.
15
15
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
+
16
28
## {% linkable_title Logs %}
17
29
18
30
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