diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss index e7bf78e4738..a52577199fa 100644 --- a/sass/custom/_paulus.scss +++ b/sass/custom/_paulus.scss @@ -218,16 +218,17 @@ p.note { } .advanced-installs-container { - #debian-install, #fedora-install, .advanced-installs { + + #upstart-install, #systemd-install, .advanced-installs { display: none; } label.menu-selector { display: inline-block; text-align: center; - padding: 10px; + padding: 20px; white-space: nowrap; - border-bottom: 2px solid $grayLight; + border-bottom: 5px solid $grayLight; transition: border-bottom-color .5s; } @@ -235,19 +236,19 @@ p.note { margin-left: 10px; } - #debian-install:checked ~ .menu-selector.debian, - #fedora-install:checked ~ .menu-selector.fedora + #upstart-install:checked ~ .menu-selector.upstart, + #systemd-install:checked ~ .menu-selector.systemd { border-bottom-color: $blue; } - #debian-install:checked ~ .advanced-installs.debian, - #fedora-install:checked ~ .advanced-installs.fedora + #upstart-install:checked ~ .advanced-installs.upstart, + #systemd-install:checked ~ .advanced-installs.systemd { display: block; } .advanced-installs { - margin-top: 20px; + margin-top: 30px; } } diff --git a/source/getting-started/advanced.markdown b/source/getting-started/advanced.markdown index 24c45d73377..bf2cf5698d9 100644 --- a/source/getting-started/advanced.markdown +++ b/source/getting-started/advanced.markdown @@ -12,34 +12,46 @@ footer: true Here are some general tutorials on how to setup some of the more advanced deployments that are frequently requested.
- - - - + + + + -
-**Debian Deamon** -

Debian based systems, including Ubuntu and Raspbian for the Raspberry Pi use an application called Init to manage daemon services. Init will launch init scripts that are located in the directory /etc/init.d/. A sample init script for Debian based systems is maintained in this project.

-

To install this script, download it, tweak it to you liking, and install it by following the directions in the header. This script will setup Home Assistant to run when the system boots. To start/stop Home Assistant manually, issue the following commands: +

+Many linux distributions use the Upstart system (or similar) for managing daemons. Typically, systems based on Debian 7 or previous use Upstart. This includes Ubuntu releases before 15.04 and all current Raspian releases. If you are unsure if your system is using Upstart, you may check with the following command: + +```bash +ps -p 1 -o comm= +``` + +If the preceding command returns the string `init`, you are likely using Upstart. + +Upstart will launch init scripts that are located in the directory /etc/init.d/. A sample init script for systems using Upstart is maintained by this project. + +To install this script, download it, tweak it to you liking, and install it by following the directions in the header. This script will setup Home Assistant to run when the system boots. To start/stop Home Assistant manually, issue the following commands: ```bash sudo service hass-daemon start sudo service hass-daemon stop ``` -

-

When running Home Assistant with this script, the configuration directory will be located at /var/opt/homeassistant. This directory will contain a verbose log rather than simply an error log.

+When running Home Assistant with this script, the configuration directory will be located at /var/opt/homeassistant. This directory will contain a verbose log rather than simply an error log. -

When running daemons, it is good practice to have the daemon run under its own user name rather than the default user's name. Instructions for setting this up are outside the scope of this document.

-
+When running daemons, it is good practice to have the daemon run under its own user name rather than the default user's name. Instructions for setting this up are outside the scope of this document. +
-
-**Fedora Daemon** -

If you want that Home Assistant is lauched automatically, an extra step is needed to setup systemd. You need a service file to control Home Assistant with systemd.

- +
+Newer linux distributions are trending towards using systemd for managing daemons. Typically, systems based on Fedora or Debian 8 or later use systemd. This includes Ubuntu releases including and after 15.04, CentOS, and Red Hat. If you are unsure if your system is using systemd, you may check with the following command: + +```bash +ps -p 1 -o comm= +``` + +If the preceding command returns the string `systemd`, you are likely using systemd. + +If you want Home Assistant to be launched automatically, an extra step is needed to setup systemd. You need a service file to control Home Assistant with systemd. ```bash su -c 'cat <> /lib/systemd/system/home-assistant.service @@ -56,7 +68,7 @@ WantedBy=multi-user.target EOF' ``` -

You need to reload systemd to make the daemon aware of the new configuration. Enable and launch Home Assistant after that.

+You need to reload systemd to make the daemon aware of the new configuration. Enable and launch Home Assistant after that. ```bash sudo systemctl --system daemon-reload @@ -64,7 +76,7 @@ sudo systemctl enable home-assistant sudo systemctl start home-assistant ``` -

If everything went well, sudo systemctl start home-assistant should give you a positive feedback.

+If everything went well, sudo systemctl start home-assistant should give you a positive feedback. ```bash $ sudo systemctl status home-assistant -l @@ -77,11 +89,11 @@ $ sudo systemctl status home-assistant -l [...] ``` -

To get Home Assistant's logging output, simple use journalctl.

+To get Home Assistant's logging output, simple use journalctl. ```bash sudo journalctl -f -u home-assistant ``` -
+
###[« Back to Getting Started](/getting-started/index.html) diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index 70f072a9a4a..bb93f58ee07 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -74,7 +74,7 @@ hass \-\-open-ui

Troubleshooting

-

If you run into any issues, please see the troubleshooting page. It contains solutions to many of the common issues.

+

If you run into any issues, please see the troubleshooting page. It contains solutions to many of the more commonly encountered issues.

For additional help, in addition to this site, there are three sources: