remarkable_printer/install.sh

systemctl stop printer.service || true
systemctl stop printer.socket || true
mkdir -p /home/root/bin
cd /home/root/bin
wget -O release.zip http://github.com/evidlo/remarkable_printer/releases/latest/download/release.zip
unzip -o release.zip
mv printer.service /etc/systemd/system
mv printer.socket /etc/systemd/system
systemctl daemon-reload
systemctl enable --now printer.socket
rm printer.x86 release.zip
stop printer service before installing 2021-03-28 19:42:20 -04:00			`systemctl stop printer.service \|\| true`
Update the install script to ensure it works with recent project state 2024-01-15 14:46:30 -05:00			`systemctl stop printer.socket \|\| true`
add install script 2020-12-18 02:02:08 -05:00			`mkdir -p /home/root/bin`
			`cd /home/root/bin`
update install script 2020-12-18 02:27:32 -05:00			`wget -O release.zip http://github.com/evidlo/remarkable_printer/releases/latest/download/release.zip`
			`unzip -o release.zip`
add install script 2020-12-18 02:02:08 -05:00			`mv printer.service /etc/systemd/system`
socket-activate printer Previous to this commit, the printer needs to continuously run in the background, even if it doesn't do much most of the time, to keep the socket open and handle incoming connections. This commit hands over handling the open socket to systemd and the printer-code gets started by systemd only when there is something incoming on the socket. The printer itself then takes over the socket from systemd, handles the incoming data and exits afterwards, returning socket management to systemd again. This reduces running processes as well as the memory footprint of the running system. 2020-12-27 09:34:58 -05:00			`mv printer.socket /etc/systemd/system`
add install script 2020-12-18 02:02:08 -05:00			`systemctl daemon-reload`
socket-activate printer Previous to this commit, the printer needs to continuously run in the background, even if it doesn't do much most of the time, to keep the socket open and handle incoming connections. This commit hands over handling the open socket to systemd and the printer-code gets started by systemd only when there is something incoming on the socket. The printer itself then takes over the socket from systemd, handles the incoming data and exits afterwards, returning socket management to systemd again. This reduces running processes as well as the memory footprint of the running system. 2020-12-27 09:34:58 -05:00			`systemctl enable --now printer.socket`
add install script 2020-12-18 02:02:08 -05:00			`rm printer.x86 release.zip`