From 359496de1e2f70976762c2671382fad09c153078 Mon Sep 17 00:00:00 2001 From: NeLLyMerC Date: Sat, 4 Mar 2017 10:39:06 -0500 Subject: [PATCH] Update step 1 to add group (#2194) Following the directions as is yielded an error at step 2 when running `sudo chown homeassistant:homeassistant /srv/homeassistant` since there are no directions prior to make a group. --- source/_docs/installation/virtualenv.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_docs/installation/virtualenv.markdown b/source/_docs/installation/virtualenv.markdown index 613b3ecd7c4..7541acba702 100644 --- a/source/_docs/installation/virtualenv.markdown +++ b/source/_docs/installation/virtualenv.markdown @@ -23,12 +23,13 @@ $ sudo apt-get install python-pip python3-dev $ sudo pip install --upgrade virtualenv ``` -### {% linkable_title Step 1: Create a Home Assistant user %} +### {% linkable_title Step 1: Create a Home Assistant user & group %} This step is optional, but it's a good idea to give services like Home Assistant their own user. It gives you more granular control over permissions, and reduces the exposure to the rest of your system in the event there is a security related bug in Home Assistant. This is a reasonably Linux oriented step, and will look different on other operating systems (or even other Linux distributions). ```bash $ sudo adduser --system homeassistant +$ sudo addgroup homeassistant ``` Home Assistant stores its configuration in `$HOME/.homeassistant` by default, so in this case, it would be in `/home/homeassistant/.homeassistant`