I've given up trying to install Calckey :calckey: manually. I've spent about 3 days on this, and I'm done. :misato_bored_pocky:
I can run it great as a Docker container :docker:, I can run it great on "bare metal" using the ubuntu.sh installer script :ubuntu:, but I cannot for the life of me successfully install and run it manually. :misato_blush:
Both the Docker deployment and the "bare metal" deployment via the installer script are fully functioning and stable. I'm just going to make peace with it and assume that all will be fine in the long term. :misato_sip:
If someone more competent than I and who knows what they're doing wants to hold my hand and walk me through this one day, then I'd be more than thrilled to volunteer the labor in using the experience to write a detailed installation guide for would-be maintainers.
@kainoa@calckey.social node installed normally with nvm put it + npm within environments in the user home directory (also where Calckey gets installed) but keeps throwing errors about unable to locate node in /use/bin/env and trying to run npm from /use/bin/npm even though that's not where it is and not the path that was given to it from whereis node or whereis npm. I don't know, I'm just over my head. I tried dissecting the ubuntu.sh script as well illuminate and interpolate unknowns. Honestly I got pretty far considering my novice experience in hobby systems administration.
@kainoa@calckey.social Can't seem to get npm to start node from the systemd daemon created. Starting it manually from the calckey directory with pnmp boots it up but full of errors, leading me to believe other things are also misconfigured. :misato_oops:
@adiz@outerkosm.us I'd say give that a try. Systemd really struggles with node sometimes. You can also sync pm2 with systemd with sudo pm2 startup && pm2 save