Issues with setting up webserver on Raspberry Pi B3+

[AMP3RAGE]

Hi. I was asked by Orob to post here what I was posting on the Makerverse forum. Here goes:

I've successfully installed the Makerverse web server on a fresh install of Raspberry Pi. The setup looks like this:

• OS: raspios-bullseye-arm64-lite
• Model: B3+

Note: I followed the installation instructions fastidiously. Nevertheless, it did NOT work right out of the box. I had to install NodeJS. I also had to modify the /home/{my login}/makerverse/bin/launch file to use /home/{my login}/ rather than home/**node** as the root directory for the install. Otherwise docker would throw an error every time I tried to launch the server. Once I did that, the webserver booted just fine. Awesome! I was then able to plug in the brains and I was able to connect up to it just fine! I spent a couple hours running the calibration and was able to get it under 3mm! Huzzah! Well, then I shut everything down, went to bed, and today when I came back to use my machine... lo and behold... no workspace! Nada! It's like I did a fresh new install! I checked the logs (docker logs makerverse and the system logs with journalctl -xe) and no errors! In fact, the logs show it launching makerverse using home/{my login}/ as the root for the project. So... what the $@#(???? As a test I did a quick new setup. I then shut everything down, rebooted, and nada! No workspace again!

All that background to ask... So... How do I get the webserver to save the workspace?

Thanks tons (in advance)! This is going to be a sweet setup once I have it all working!

EDIT 01: I SFTP'd all the files from the RPi to my Windows laptop. I then did a comparison of the info in the .makerverse file from the RPi and the one on my desktop (from the standalone Makerverse app). They are vastly different. Here is the FULL text from the .makerverse I pulled from the RPi:

{
  "watchDirectory": "/home/node/gcode",
  "workspaces": [],
  "mountPoints": [
    {
      "route": "/tablet",
      "target": "/home/node/makerverse/widgets/cncjs-shopfloor-tablet/src/"
    }
  ],
  "state": {
      "checkForUpdates": true,
      "prereleases": false,
      "controller": {
          "exception": {
              "ignoreErrors": false
          }
      },
      "allowRemoteAccess": true
  },
  "commands": [
    {
      "id": "5b98d27e-79e7-4fcd-afbe-8de87b558df3",
      "mtime": 1600691535812,
      "enabled": true,
      "title": "Restart Makerverse",
      "commands": "pkill node"
    }
  ]
}

Note the /home/node/... references! There they are again! So, I modified this file, replacing every reference to "node" in filepaths with my profile name. I uploaded the file. Rebooted the RPi. Still same behavior. I keep using "cat .makerverse" to check if it ever gets modified... and nope! Never any changes to it. Also, please note the empty workspaces array ("workspaces": [],) The one on my PC has all the config data in the array for the setup I did using the standalone app on my laptop. So... why is it not getting saved on the RPi? Very curious...

EDIT 02: After thinking about this some more it dawned on me that I can keep searching for every reference to "node" in filepaths in every file in the makerverse install, or I can jump on the "home/node" bandwagon (so to speak). So, (not wanting to fully commit to creating a user login with the name "node"... because that's just plain silly!) I added a symbolic link from /home/node pointing to /home/{my login}. The link works fine. I can cd /home/node and it will take me to /home/{my login}. I rebooted the RPi. The symbolic link is still there, but saving a workspace still doesn't actually save anything. Still NO changes to .makerverse file! Now I'm really stuck!

Ideas? Thanks in advance!

[AMP3RAGE]

Also, There is no "node" user. But Makerverse has references to a /home/node filepath EVERYWHERE! For example. If I run docker container ls I see the following output for the makerverse container:

CONTAINER ID   IMAGE                    COMMAND                  CREATED          STATUS          PORTS                                       NAMES
99daca45d67a   makerverse/core:latest   "/home/node/bin/dock…"   37 minutes ago   Up 37 minutes   0.0.0.0:8000->8000/tcp, :::8000->8000/tcp   makerverse

Note the reference to the /home/node/bin/docker path... This is a problem. Or at least I think it is.