blob: b25bd68bfe29dbf605ea939ebc37f34b3f2aa30e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
post_install() {
cat <<-EOF
Start homebridge + ui with systemd:
$ systemctl enable --now homebridge
Caveats:
1) /usr/bin/hb-service places files all over the system, and it will
also modify /etc/sudoers. It is also capable of installing an
alternative binary of Node.js. It is recommended to *never* use it.
2) Installing or upgrading plugins from the web ui invokes npm install
globally (/usr/lib/node_modules). You can alternatively package plugins as AUR
packages. Sticking with verified plugins can also provide a higher level of
security.
See: https://github.com/homebridge/homebridge/wiki/Verified-Plugins
3) To give permissions to the web ui to poweroff/reboot the machine and
install plugins, create a drop-in file in /etc/sudoers.d similar to:
homebridge ALL=(ALL) NOPASSWD:SETENV: /usr/bin/npm, /usr/bin/shutdown, /usr/local/bin/npm
4) The web ui runs commands with sudo in various places.
You have been warned.
5) It is recommended to run homebridge with a supported Node.js version.
Currently nodejs-lts-iron (Node.js 20) is the recommended version.
6) To use systemd-resolved as the mDNS resolver, set up systemd-resolved mDNS
and then follow these instructions:
https://github.com/homebridge/homebridge/wiki/mDNS-Options#systemd-resolved-linux-only-experimental
EOF
}
post_upgrade() {
post_install
}
|