* Fix links appearance
For some reason the links inside p tag are not rendered properly, but inside br tag it works properly.
* Fix links
Better fix (by adding space)
* 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
* Fixed URLs
.md were moved from 'hassbian-scripts/blob/master/docs' to 'hassbian-scripts/tree/dev/docs/suites'
* Fixed Hassbian 404 URLs
Also updated the list with more available scripts. Homebridge was not found in the hassbian-scripts repository so it was deleted
* Update to the macOS guide
1. Updated the Python version
2. Changed it to a venv install to avoid people breaking things by accident
3. Linked to the auto-start guide
4. Removed link to the outdated video
* Update macos.markdown
* ✏️ Tweaks
* ✏️ Tweak
I'm guessing the -y was meant to be on pkg upgrade, instead?
from pkg help update:
pkg update [-fq] [-r reponame]
pkg update [--{force,quiet}] [--repository reponame]
* Update install docs for FreeNAS 11.2
This includes some best-practice improvements (such as running Home
Assistant as a limited-access user vs root), using Python 3.7 to install
and adding a BSD-style service to manage and test configuration.
* Fix typo
* Adding upgrade details
Adding details here on how to upgrade and run specific versions, rather than leaving them as incomplete generic steps in the Updating page
* ✏️ Tweaks
I get
```
pi@hassbian:~ $ sudo hassbian-config upgrade homeassistant
/usr/local/bin/hassbian-config: line 140: /opt/hassbian/suites/upgrade_homeassis tant.sh: No such file or directory
/usr/local/bin/hassbian-config: line 141: homeassistant-upgrade-package: command not found
```
when running what it currently is.
adding the dash in home-assistant fixes the issue
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.
* Updates for python36 and scl
Latest changes to installing the scl environment don't include the scl command, scl-utils is needed along w/ the proper repository in Centos7 to be enabled via RH and then downloaded to the environment which you are building and then SCL commands will work and setting python environment for bash will work too.
* Minor changes
* 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
* Remove group gpio from Installation instructions for Fedora
That group doesn't exist on Fedora by default. I believe it makes more
sense to add homeassistant to that group later when that group needs to
be created.
* sudo to homeassistant before virtualenv is activated on Fedora
Very similar approach to Debian-based installation needs to be done
here. In the previous block of commands user homeassistant is created
and directories are chowned to him.
If one would try to run followup pip3 install or even hass itself as
current user he wouldn't be able to write to those directories or that
homeassistant user would be just useless.
Added instructions for development libraries (build-essential libssl-dev libffi-dev) required for cffi, bcrypt, and cryptography. This may not be necessary on some Debian based systems for desktops with dev libraries installed but for server installations (I tested with Armbian) this is required.
