Arch Linux User Repository

@tronicdude apologies the supplied service file is missing the [Install] section. I missed this because my own installation pulls the service in through a Wants= relationship to another unit. You can start the service manually but it cannot be enabled, i.e. started automatically at boot:

systemctl start actual.service

I will correct the service file now to add the missing section, keep an eye out for 24.1.0-4.

@emphire the package dependency is nodejs allowing any version to be installed, i.e. any packaged that provides nodejs. However you must build the package with the same version you have installed on your target machine - or you will receive errors such as this. This is most commonly a problem with a clean chroot where it is easy to let nodejs to be installed to the chroot (v21 in the repos at the moment) but if you have a different version, e.g. nodejs-lts-hydrogen installed (v18) on your target machine then it will not run. If using a clean chroot, you must manually install the desired provider of nodejs first before building the package.

> sudo systemctl enable --now actual-server
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.

Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

Not exactly sure how to start this thing

I'm getting the following error when attempting to start the server:

 Started Actual Server.
]: Checking if there are any migrations to run for direction "up"...
]: Rejection: Error: The module '/usr/share/webapps/actual-server/node_modules/better-sqlite3/build/Release/better_sqlite3.node'
]: was compiled against a different Node.js version using
]: NODE_MODULE_VERSION 115. This version of Node.js requires
]: NODE_MODULE_VERSION 108. Please try re-compiling or re-installing
]: the module (for instance, using `npm rebuild` or `npm install`).
]:     at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
]:     at Module.load (node:internal/modules/cjs/loader:1119:32)
]:     at Module._load (node:internal/modules/cjs/loader:960:12)
]:     at Module.require (node:internal/modules/cjs/loader:1143:19)
]:     at require (node:internal/modules/cjs/helpers:119:18)
]:     at bindings (/usr/share/webapps/actual-server/node_modules/bindings/bindings.js:112:48)
]:     at new Database (/usr/share/webapps/actual-server/node_modules/better-sqlite3/lib/database.js:48:64)
]:     at openDatabase (file:///usr/share/webapps/actual-server/src/db.js:57:30)
]:     at getAccountDb (file:///usr/share/webapps/actual-server/src/account-db.js:12:18)
]:     at Migration.up (file:///usr/share/webapps/actual-server/migrations/1694360479680-create-account-db.js:4:9) {
]:   code: 'ERR_DLOPEN_FAILED'
]: }
 actual-server.service: Deactivated successfully.
 actual-server.service: Consumed 1.148s CPU time.

updated to depend on nodejs and bumped to latest upstream.

Thanks @zachasme for pointing this out. I couldn't get this to build with nodejs v20 in a clean chroot which is why I limited it to nodejs-lts-hydrogen. I'll look into it though because it works outside a chroot.

Hi there! Would you be able to change the depends array to refer to nodejs instead of nodejs-lts-hydrogen directly? This is how many other node-dependant packages on AUR works e.g. https://aur.archlinux.org/packages/mongosh, which allows users to use any package providing nodejs (including lts-hydrogen).