From ebea4ecf2749c86dcbdf990e3d0ad31898447200 Mon Sep 17 00:00:00 2001 From: Travis CI Date: Fri, 13 May 2016 20:25:49 +0000 Subject: [PATCH] Site updated at 2016-05-13 20:25:49 UTC --- atom.xml | 2 +- blog/categories/community/atom.xml | 2 +- blog/categories/esp8266/atom.xml | 2 +- blog/categories/how-to/atom.xml | 2 +- blog/categories/ibeacons/atom.xml | 2 +- blog/categories/internet-of-things/atom.xml | 2 +- blog/categories/mqtt/atom.xml | 2 +- blog/categories/organisation/atom.xml | 2 +- blog/categories/owntracks/atom.xml | 2 +- blog/categories/presence-detection/atom.xml | 2 +- .../public-service-announcement/atom.xml | 2 +- blog/categories/release-notes/atom.xml | 2 +- blog/categories/survey/atom.xml | 2 +- blog/categories/talks/atom.xml | 2 +- blog/categories/user-stories/atom.xml | 2 +- blog/categories/video/atom.xml | 2 +- blog/categories/website/atom.xml | 2 +- .../installation-virtualenv/index.html | 47 +++++++++---------- sitemap.xml | 12 ++--- 19 files changed, 46 insertions(+), 47 deletions(-) diff --git a/atom.xml b/atom.xml index cc84cece0d..c106b2bca7 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 16be318b60..611f68ec79 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 327f9970c7..e22e27cd54 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index dbfbade948..b30cc7f8b2 100644 --- a/blog/categories/how-to/atom.xml +++ b/blog/categories/how-to/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: How-To | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index d8a8f56c9b..f84387492d 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index 58d0bc7fe2..12e3e7b198 100644 --- a/blog/categories/internet-of-things/atom.xml +++ b/blog/categories/internet-of-things/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Internet-of-Things | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 5e1e1ed055..4809a1ed38 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index 91ce7d56c5..24b033a3e1 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 524fee69ed..ddc3a2c4a3 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index caedd9c9e3..45ca228617 100644 --- a/blog/categories/presence-detection/atom.xml +++ b/blog/categories/presence-detection/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Presence-Detection | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml index e2618494bf..bc9a8d4039 100644 --- a/blog/categories/public-service-announcement/atom.xml +++ b/blog/categories/public-service-announcement/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Public-Service-Announcement | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 3ef59f6c54..2bb8cef45e 100644 --- a/blog/categories/release-notes/atom.xml +++ b/blog/categories/release-notes/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Release-Notes | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 464417d728..29b870714d 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 3c89931e75..3662ba8789 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index 32b41fa1d5..023e6a7810 100644 --- a/blog/categories/user-stories/atom.xml +++ b/blog/categories/user-stories/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: User-Stories | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index 0ee8c01040..ff437dea1e 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 0dbe9fa2c4..384a0689c0 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2016-05-13T19:12:11+00:00 + 2016-05-13T20:25:08+00:00 https://home-assistant.io/ diff --git a/getting-started/installation-virtualenv/index.html b/getting-started/installation-virtualenv/index.html index 2f40a6b8bf..caabc8c27d 100644 --- a/getting-started/installation-virtualenv/index.html +++ b/getting-started/installation-virtualenv/index.html @@ -89,11 +89,11 @@
-

There are several reasons why it makes sense to run Home Assistant in a virtualenv. A virtualenv encapsulates all aspect of a Python environment within a single directory tree. That means the Python packages you install for Home Assistant won’t interact with the rest of your system and vice-versa. It means a random upgrade for some other program on your computer won’t break HA, and it means you don’t need to install a bunch of Python packages as root.

+

There are several reasons why it makes sense to run Home Assistant in a virtual environment. A virtualenv encapsulates all aspect of a Python environment within a single directory tree. That means the Python packages you install for Home Assistant won’t interact with the rest of your system and vice-versa. It means a random upgrade for some other program on your computer won’t break Home Assitant, and it means you don’t need to install Python packages as root.

-

Virtualenvs are pretty easy to setup. This example will walk through one method of setting one up (there are certainly others). We’ll be using Debian in this example (as many HA users are running Raspbian on a Raspberry Pi), but all of the Python related steps should be the same on just about any platform.

+

Virtualenvs are pretty easy to setup. This example will walk through one method of setting one up (there are certainly others). We’ll be using Debian in this example (as many Home Assistant users are running Raspbian on a Raspberry Pi), but all of the Python related steps should be the same on just about any platform.

-

Step 0: Install some dependencies

+

Step 0: Install some dependencies

sudo apt-get update
@@ -104,9 +104,9 @@ sudo pip install --upgrade virtualenv
-

Step 1: Create a Home Assistant user

+

Step 1: Create a Home Assistant user

-

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 HA. This is a reasonably Linux oriented step, and will look different on other OS’s (or even other Linux distros).

+

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).

sudo adduser --system hass
@@ -114,7 +114,7 @@ sudo pip install --upgrade virtualenv
-

Home Assistant stores its config in $HOME/.homeassistant by default, so in this case, it would be in /home/hass/.homeassistant

+

Home Assistant stores its configuration in $HOME/.homeassistant by default, so in this case, it would be in /home/hass/.homeassistant

If you plan to use a Z-Wave controller, you will need to add this user to the dialout group

@@ -124,9 +124,9 @@ sudo pip install --upgrade virtualenv
-

Step 2: Create a directory for Home Assistant

+

Step 2: Create a directory for Home Assistant

-

This can be anywhere you want, but I generally put stuff related to servers in /srv. You also need to change the ownership of the directory to the user you created above (if you created one)

+

This can be anywhere you want, but I generally put stuff related to servers in /srv. You also need to change the ownership of the directory to the user you created above (if you created one)

sudo mkdir /srv/hass
@@ -134,8 +134,7 @@ sudo chown hass /srv/hass
- -

Step 3: Become the new user

+

## Step 3: Become the new user

This is obviously only necessary if you created a ‘hass’ user, but if you did, be sure to switch to that user whenever you install things in your virtualenv, otherwise you’ll end up with mucked up permissions.

@@ -147,7 +146,7 @@ sudo chown hass /srv/hass

The ‘su’ command means ‘switch’ user. We use the ‘-s’ flag because the hass user is a system user and doesn’t have a default shell by default (to prevent attackers from being able to log in as that user).

-

Step 4: Set up the virtualenv

+

Step 4: Set up the virtualenv

All this step does is stick a Python environment in the directory we’re using. That’s it. It’s just a directory. There’s nothing ‘special’ about it, and it is entirely self-contained.

@@ -159,7 +158,7 @@ sudo chown hass /srv/hass -

Step 5: Activate the virtualenv

+

Step 5: Activate the virtualenv

source /srv/hass/bin/activate
@@ -169,9 +168,9 @@ sudo chown hass /srv/hass
 
 
After that, your prompt should include ‘(hass)’.

 
-
Step 6: Install Home Assistant

+
 Step 6: Install Home Assistant

 
-
Once your virtualenv has been activated, you don’t need to ‘sudo’ any of your pip commands. Pip will be installing things in the virtualenv, which our ‘hass’ user has permission to modify.

+
Once your virtualenv has been activated, you don’t need to sudo any of your pip commands. Pip will be installing things in the virtualenv, which our ‘hass’ user has permission to modify.

 
 

   
(hass)pip3 install --upgrade homeassistant
@@ -181,9 +180,9 @@ sudo chown hass /srv/hass
 
 
And that’s it… you now have Home Assistant installed, and you can be sure that every bit of it is contained in /srv/hass

 
-
Finally… Run Home Assistant

+
 Finally… Run Home Assistant

 
-
There are two ways to launch Home Assistant. If you are ‘in’ the virtualenv, you can just run hass and it will work as normal. If the virtualenv is not activated, you just use the ‘hass’ executable in that bin directory I mentioned earlier. There is one caveat… Because Home Assistant stores it’s config in the user’s home directory, we need to be the hass user.

+
There are two ways to launch Home Assistant. If you are ‘in’ the virtualenv, you can just run hass and it will work as normal. If the virtualenv is not activated, you just use the hass executable in the bin directory mentioned earlier. There is one caveat… Because Home Assistant stores it’s configuration in the user’s home directory, we need to be the user hass user or specify the configuration with -c.

 
 

   
sudo -u hass -H /srv/hass/bin/hass
@@ -191,21 +190,21 @@ sudo chown hass /srv/hass
 

 

 
-
The ‘-H’ flag is important. It sets the $HOME environment variable to /home/hass so hass can find its configs.

+
The ‘-H’ flag is important. It sets the $HOME environment variable to /home/hass so hass can find its configuration.

 
-
Upgrading Home Assistant

+
 Upgrading Home Assistant

 
-
Upgrading HA is simple, just repeat steps 3, 5 and 6.

+
Upgrading Home Assistant is simple, just repeat steps 3, 5 and 6.

 
-
Starting Home Assistant on boot

+
 Starting Home Assistant on boot

 
-
The autostart instructions on home-assistant.io will work just fine, just be sure to replace /usr/bin/hass with /srv/hass/bin/hass and specify the ‘hass’ user where appropriate.

+
The autostart instructions will work just fine, just be sure to replace /usr/bin/hass with /srv/hass/bin/hass and specify the hass user where appropriate.

 
-
Installing python-openzwave

+
 Installing python-openzwave

 
-
If you want to use Z Wave devices, you’ll need to install python-openzwave in your virtualenv. This requires a small tweak to the instructions on home-assistant.io

+
If you want to use Z-Wave devices, you will need to install python-openzwave in your virtualenv. This requires a small tweak to the instructions on home-assistant.io

 
-
Install the dependencies as normal (note: you’ll need to do this as your normal user, since ‘hass’ isn’t a sudoer).

+
Install the dependencies as normal (Note: you’ll need to do this as your normal user, since ‘hass’ isn’t a sudoer).

 
 

   
$ sudo apt-get install cython3 libudev-dev python3-sphinx python3-setuptools
diff --git a/sitemap.xml b/sitemap.xml
index a9e1781049..4c21e23df3 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1600,26 +1600,26 @@
     
   
     https://home-assistant.io/demo/frontend.html
-    2016-05-13T19:11:20+00:00
+    2016-05-13T20:24:27+00:00
   
   
     https://home-assistant.io/demo/index.html
-    2016-05-13T19:11:20+00:00
+    2016-05-13T20:24:27+00:00
   
   
     https://home-assistant.io/googlef4f3693c209fe788.html
-    2016-05-13T19:11:20+00:00
+    2016-05-13T20:24:27+00:00
   
   
     https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-    2016-05-13T19:11:20+00:00
+    2016-05-13T20:24:27+00:00
   
   
     https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-    2016-05-13T19:11:20+00:00
+    2016-05-13T20:24:27+00:00
   
   
     https://home-assistant.io/static/mdi-demo.html
-    2016-05-13T19:11:20+00:00
+    2016-05-13T20:24:27+00:00