Joseph Huckaby

@ioqy Start on boot only works if node is installed under one of the standard Linux binary locations: ```sh PATH=$PATH:/usr/bin:/bin:/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin ``` You can symlink it there using a command such...

@ioqy I apologize. Node.js recently changed how they do installs. It used to always be installed in `/usr/bin/node` or `/usr/local/bin/node`, like for the last 15 years. I never expected this...

@ioqy Hmmm, I dunno. I'm not entirely sure what `~/.nvm/nvm.sh use --lts` does, and if the user would always want that. They may be running a non-LTS version of Node,...

Okay, so, we're on the right track here, but we need a slightly different command. The `nvm.sh` script is NOT executable, so we need to test and exec it differently....

All fixed in [Cronicle v0.9.66](https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.66). Tested boot on Ubuntu 24 with Node.js LTS installed via nvm.

> The only thing is that when the nvm default is set to a non LTS version, just sourcing nvm (the command . ~/.nvm/nvm.sh) will then set node to the...

@ioqy Ohhhhh! I'm so sorry, I had no idea that verbiage was still in the docs. I'll reword that so it's more of a suggestion rather than a requirement. It...

Reworded. Thanks!

Yeah, Cronicle **really** wants to live in `/opt/cronicle`. There are a bunch of things that expect that base path, particularly the `control.sh` script and all the CLI commands. I'm really...

It's really difficult to help you when you don't use the GitHub New Issue Template. We provide that for a reason, namely to collect key information to help us troubleshoot...