# add paragraph to explain how to update docker-compose.yml example for macOS
# The TZ issue wasn't specific to `boot2docker`
# Add details link for net:host vs port: conflict
# Add details link for TZ issue
The basic venv install guide mentions this step so we should make sure the advanced guide has the same step in the same location.
The note about the advanced guide is there to reassure the user they are on the correct page even though the raspberry pi is heavily mentioned here.
Some users find difficulty when installing or applying updates however, once they switch to the advanced guide those problems go away.
I am not sure if the code block will work for the note so feel free to remove it if it does not :)
We should provide proper guidance to the user about the importance of release notes and paying attention to breaking changes. A common error users face while updating home assistant is not paying attention to the breaking changes. If the user has not done an update in sometime they may also forget about previous breaking changes that still stand.
Fix symbolic links to python3 and homeassistant executable. Fix permissions and ownership to homeassistant directory to allow writing to home-assistant.log.
Given that people using Windows keep grabbing the alpha releases of 3.7, I've added a recommendation of Python 3.6, and a note about not downloading alpha or beta versions, and how to identify them.
* Update freenas.markdown
The example provided for a chained command to mkdir /home and /home/.homeassistant was missing the second mkdir command. A copy and paste of this example would fail.
* Update freenas.markdown
Updated mkdir commands to use '-p' option.
* Update guide for clarity
Recommends auto-starting by default, with manual starting as an option. Explicitly pull out the upgrade steps (since it also involves stopping HA first). Recommend install as a dedicated user.
* Minor changes
* Removes extraneous paragraph from docker documentation
It looks like this line was intended to go somewhere else, but got
erroneously bumped into the `Restart` section.
* Adds instructions to expose devices when deploying under docker
* Adds info about `docker-compose.yml` configuration to docker deployments
The docker command is pretty complicated and doesn't support automated
restarts. I think most users with want to use `docker-compose` (or
`docker swarm`) to deploy.
Provide information to users so that they can determine the impact of the latest version on their system. Updates many times require changes to configuration, renaming of entities (z-wave for example), and deprecation of features,
Using above instructions container name includes the dash.
shiny % docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a9be19e6c76a homeassistant/home-assistant "python -m homeass..." 5 minutes ago Up About a minute 0.0.0.0:8123->8123/tcp home-assistant
shiny % docker restart homeassistant
Error response from daemon: No such container: homeassistant
[1] 67676 exit 1 docker restart homeassistant
shiny !1! % docker restart home-assistant
home-assistant
* update to synology docker install page
Unfortunately the Synology GUI way of installing Home Assistant through docker does not allow access to the USB devices to use a Bluetooth or Z-Wave radio (has to be done via ssh) - User Phil Hawthorne has provided great instructions on his blog to access these devices - so wondered if it was acceptable to provide a link (otherwise it would require adding quite a lot of info to the page)
Regards,
James
* Make a note
typo - the instructions suggest calling your container "homeassistant" but then refer to restarting a container called "home-assistant"
typo - "lose" instead of "loose" & "a" instead of "an"
additional - web interface accessible using http://synologyIP:8123
additional - how to restart from synology
