* Remove host/netsh commands from docker directives
Added -p 8123:8123 to the Windows docker command line. Seems more reliable and easier for users.
Add ports to docker-compose.yaml files for easier launches..
* revert requested items.
* ✏️ Tweaks
* Sets front matter defaults
* Removes default front matter from section templates/pages
* Removes default front matter from addon pages
* Removes default front matter from integration pages
* Removes default front matter from posts
* Removes default front matter from docs pages
* Removes default front matter from other pages
* Fixes blog category pages
* Automatically create linkable headers
* Visually improve position of linkable header chain icon
* Do not auto link headers on homepage
* Remove linkable_title everywhere
* 🚑 Re-instante linkable_title plugin as NOOP
See also https://github.com/home-assistant/home-assistant/issues/20260, the --init argument makes sure that the python service does not run with PID 1 which on some host systems can not be killed, i.e. restarting the service from within the UI is unreliable without that argument.
* Added Synology Z-Wave USB stick configuration
added Docker Terminal command for creating a new Synology Docker container with access to a connected Z-Wave USB stick.
Would be good to add similar config switches for the other platforms too?
* Apply suggestions from code review
trying my best to stumble through this. I'm still very new to this and have only read the Home Assistant doco on contributing. Hopefully i have done this right?
* ✏️ Tweaks
The docker compose examples have you create a service called 'web', which will create web_1 docker container. Other references within the documents say to run `docker restart home-assistant`, yet this docker container does not exist when using the docker compose examples. Updated compose so they will have a standard name for the container that is created.
# 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
* 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.
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
