Where does the helper scripts log to?

[midnight crystal]

I'm new to Proxmox, and Helper-Scripts. I thought I'd try my hand at writing a new Helper Script by copying code from existing scripts (ct/homarr.sh and install/homarr-install.sh). I forked the repo, and pushed up my new files to it, and can run the shell command to install my new Helper Script, and I do not get any errors reported in the Helper Scripts UI, but, I am pretty sure something is failing along the way. The new CT is running, and is assigned a name based on the $APP variable that is set, but I do not think the app is running, nor do I think the dependencies were installed (nodejs, yarn, etc). The installer script completes too fast, in my opinion, and does not take the time it needs to install nodejs, yarn, python, etc, etc, etc.

After the installer script completes (without any visible errors), no IP address is posted in the final output of the script, indicating to me that the $IP variable is not being set by the Helper Scripts.

Access it using the following URL:
  Grist: http://:8484

I also cannot open a console on the new CT, since it requires a password (even though the script should default to "automatic login").

I went looking around for where msg_info, msg_ok, etc strings might get dumped, since they don't appear during the install process, and I cannot seem to find them in the Proxmox UI on the node, or individual CT.
I ssh'd into the node and went hunting in the /var/log folder, did some grepping, and even opened up the system.journal file (journalctl --file /var/log/journal/xxxSnipxxx/system.journal) but found no indication of the messages I'd expect to see via echo or msg_info calls inside the Helper Script I wrote.

I looked through past issues/PRs/discussions on https://github.com/community-scripts/ProxmoxVE, but was not able to find what I was looking for. Thanks in advance for any guideance on this.

[open owl]

When you create the fork, there are many files that are hardlinked to the original repo.
You need to follow the entire process from start to finish to make sure that you're remaining in your own repo to ensure that you've set up the script correctly.

For example, look at line 2 here:
https://github.com/community-scripts/ProxmoxVE/blob/main/ct/homarr.sh

If I had a copy of this script in my own repo and run it, I would instantly be redirected back to the community scripts repo where my new/edited code does not exist.

[midnight crystal]

Thanks -- I did notice that it was fetching the build.func from the original repo, but I did not follow the code paths too far. From what I gleaned, I thought it would be safe to keep that reference as it was sourcing shell functions. I did not notice any other calls that would reference other files in that repo, but, again, I did not scan the entire file.

I also assumed/hoped that I would not have to change all refs like that, as I presumed other script writers would not have to go back and forth updating URLs, etc, during development. I'll start there, and see if it turns anything else up.

I guess I further assumed that any "file not found" or "script not found" errors that could arise during install would appear in the installer UI. Seems like there are more errors being swallowed and send to /dev/null, and the overall script still reporting "success".

[midnight crystal]

Thanks again for the tip, @open owl. That change to all URLs to point to my repo is getting me further. Appreciate it!