Slow server install, quirky nohup on Raspberry Pi Zero W

[LorenAmelang]

I finally have a Trilium server!

Installing Docker on my Raspberry Pi Zero W with current Debian Bullseye failed miserably:
docker/for-linux#1347
docker/for-linux#1349

Seems there is no Packaged Install for armhf, so I tried Manual Install:

pi@raspberrypi:~ $ wget https://unofficial-builds.nodejs.org/download/release/v14.18.3/node-v14.18.3-linux-armv6l.tar.xz

pi@raspberrypi:~ $ sudo apt install libpng16-16 libpng-dev pkg-config autoconf libtool build-essential nasm libx11-dev libxkbfile-dev

pi@raspberrypi:~ $ wget https://github.com/zadam/trilium/archive/refs/tags/v0.49.5.tar.gz

The build looked normal for awhile, but then:

> [email protected] install /home/pi/trilium/trilium-0.49.5/node_modules/better-sqlite3
> prebuild-install || npm run build-release

prebuild-install WARN install No prebuilt binaries found (target=14.18.3 runtime=node arch=arm libc= platform=linux)


-->See https://github.com/prebuild/prebuild-install/issues/141


> [email protected] build-release /home/pi/trilium/trilium-0.49.5/node_modules/better-sqlite3
> node-gyp rebuild --release

make: Entering directory '/home/pi/trilium/trilium-0.49.5/node_modules/better-sqlite3/build'
  TOUCH b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
  ACTION deps_sqlite3_gyp_locate_sqlite3_target_extract_sqlite3 b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
  TOUCH Release/obj.target/deps/locate_sqlite3.stamp
  CC(target) Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o


--> Long pause here, maybe 20 minutes, no output, same pause at similar location happened again in rebuild


  AR(target) Release/obj.target/deps/sqlite3.a
  COPY Release/sqlite3.a
  CXX(target) Release/obj.target/better_sqlite3/src/better_sqlite3.o
In file included from ./src/better_sqlite3.lzz:11,
                 from ../src/better_sqlite3.cpp:4:
/home/pi/.cache/node-gyp/14.18.3/include/node/node.h:807:7: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Context>)’ to ‘node::addon_context_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Context>, void*)’} [-Wcast-function-type]
  807 |       (node::addon_context_register_func) (regfunc),                  \
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/pi/.cache/node-gyp/14.18.3/include/node/node.h:825:3: note: in expansion of macro ‘NODE_MODULE_CONTEXT_AWARE_X’
  825 |   NODE_MODULE_CONTEXT_AWARE_X(modname, regfunc, NULL, 0)
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/pi/.cache/node-gyp/14.18.3/include/node/node.h:856:3: note: in expansion of macro ‘NODE_MODULE_CONTEXT_AWARE’
  856 |   NODE_MODULE_CONTEXT_AWARE(NODE_GYP_MODULE_NAME,                     \
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~
./src/better_sqlite3.lzz:67:1: note: in expansion of macro ‘NODE_MODULE_INIT’
./src/objects/database.lzz: In static member function ‘static void Database::JS_new(const v8::FunctionCallbackInfo<v8::Value>&)’:
./src/objects/database.lzz:180:21: warning: variable ‘status’ set but not used [-Wunused-but-set-variable]
./src/util/data.lzz: In function ‘v8::Local<v8::Value> Data::GetValueJS(v8::Isolate*, sqlite3_stmt*, int, bool)’:
./src/util/data.lzz:73:92: warning: this statement may fall through [-Wimplicit-fallthrough=]
./src/util/data.lzz:73:197: note: here
./src/util/data.lzz: In function ‘v8::Local<v8::Value> Data::GetValueJS(v8::Isolate*, sqlite3_value*, bool)’:
./src/util/data.lzz:77:81: warning: this statement may fall through [-Wimplicit-fallthrough=]
./src/util/data.lzz:77:175: note: here
  SOLINK_MODULE(target) Release/obj.target/better_sqlite3.node
  COPY Release/better_sqlite3.node
  CC(target) Release/obj.target/test_extension/deps/test_extension.o
  SOLINK_MODULE(target) Release/obj.target/test_extension.node
  COPY Release/test_extension.node
rm b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
make: Leaving directory '/home/pi/trilium/trilium-0.49.5/node_modules/better-sqlite3/build'

Rebuild:

make: Entering directory '/home/pi/trilium/trilium-0.49.5/node_modules/better-sqlite3/build'
  TOUCH b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
  ACTION deps_sqlite3_gyp_locate_sqlite3_target_extract_sqlite3 b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
  TOUCH Release/obj.target/deps/locate_sqlite3.stamp
  CC(target) Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o


--> Long pause again...

The server works, so I guess these are not serious problems. But I suspect I will have to redo this long process every time the "Sync" version changes, so I'm wondering if there is a way to avoid the long pauses.

There was one other huge time sink in the installation:

pi@raspberrypi:~/trilium/trilium-0.49.5 $ nohup node src/www &
[1] 11818
pi@raspberrypi:~/trilium/trilium-0.49.5 $ nohup: ignoring input and appending output to 'nohup.out'
<-- The SSH terminal does not automatically show a new prompt here, the command just stops

If I leave the screen like that and close the terminal, the nohup fails, the Trilium server is no longer running.

If I press Enter before closing the SSH terminal, I get a normal prompt and the Trilium server remains active.

I can't imagine an explanation, or find one on the internet, but after over an hour of struggle, that seems to be how it works here.

Interesting suggestions in:
#2136
"Trouble running Trilium server on RaspberryPi"