jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-10 10:56:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Frontend development documentation (#328)

Browse Source 
* Update Frontend development documentation

I was going through this while trying to get the front end set up to work on another PR and noticed it was out of date and had trouble getting everything working.  I'm updating it to hopefully better reflect what I had to do to get it working and update the latter portion as it seems like manually building every time a change is made is no longer necessary.  Also updated the configuration.yaml example as the docs here https://developers.home-assistant.io/docs/en/frontend_development.html#configuring-home-assistant say to set up frontend.development_repo not hassio.development_repo.  

Hopefully this is correct but let me know if I'm completely misunderstanding this document as I'm pretty new to getting everything set up for local development. :)

* Switch commands from frontend back to hassio
This commit is contained in:
Phi Dong 2019-10-04 08:37:35 -07:00 committed by Paulus Schoutsen
parent 41c7defebc
commit d5df3fbb69
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/hassio_hass.md
View File

@ -21,9 +21,9 @@ $ docker inspect homeassistant | grep HASSIO_TOKEN
## Having Home Assistant connect to remote Hass.io
The connection with the supervisor is hidden inside the host and is only accessible from applications running on the host. So to make it accessible for our Home Assistant instance, we will need to route the connection to our computer running Home Assistant. We're going to do this by forwarding the API with "Remote API proxy" Add-on.
The connection with the supervisor is hidden inside the host and is only accessible from applications running on the host. So to make it accessible for our Home Assistant instance we will need to route the connection to our computer running Home Assistant. We're going to do this by forwarding the API with "Remote API proxy" add-on.
First, make sure Home Assistant will load the Hass.io component by adding `hassio:` to your `configuration.yaml` file. Next, we will need to tell Hass.io component how to connect to the remote Hass.io instance, we do this by setting the `HASSIO` and `HASSIO_TOKEN` environment variables when starting Home Assistant. Note that the `HASSIO` value is not the same as the one that we saw above and the `HASSIO_TOKEN` is available inside log output of "Remote API Add-on" (This change every restart of this Add-on!).
First, make sure Home Assistant will load the Hass.io component by adding `hassio:` to your `configuration.yaml` file. Next, we will need to tell the local Home Assistant instance how to connect to the remote Hass.io instance. We do this by setting the `HASSIO` and `HASSIO_TOKEN` environment variables when starting Home Assistant. Note that the `HASSIO` value is not the same as the one that we saw above and the `HASSIO_TOKEN` is available inside log output of "Remote API Add-on" (This changes every restart of the add-on!).
```bash
HASSIO=<IP OF HASS.IO>:80 HASSIO_TOKEN=<VALUE OF HASSIO_TOKEN> hass
@ -49,9 +49,9 @@ To build a local version of the Hass.io panel, go to the frontend repository and
```bash
cd hassio
script/build_hassio
script/develop
```
Now start Home Assistant as discussed in the previous section and it will now connect to the remote Hass.io but show your local frontend.
We're currently transitioning in how we're building the frontend so we don't have an incremental development mode just yet. For now, after making a local change, run `script/build_hassio` again.
Once you have `script/develop` the hassio panel will be rebuilt whenever you make changes to the source files.