I've blathered about this to Theno on Discord, but figured I'd catalog here.
Soma — Today at 9:16 AM
Okay, so! The LAMP route didn't matter and I was able to get my non-root user to work with it. After digging through some stack exchange posts, it looks like SQL no longer uses the my_bool function, it's just bool. I adjusted the reconnect function to just connect and it processed through which is interesting because usually connect can't be declared in scope. So, it processed through with warnings but didn't error out. However, it didn't create the game folder. I'm wondering if this has something to do with the size issue. I'm not sure if you're still in contact with Chime, but this might be some feedback for her about the directions in her distro -- at least some feedback on the directions for getting ChimeMUX working on a LAMP stack in Digital Ocean.
Soma — Today at 10:03 AM
All right, found mux-start but it says it can't open the script.conf file, which is pretty weird. Permissions are fine. For some reason the mux server got installed in the root directory, so I wonder if that has something to do with it. Maybe the mux-start command doesn't have root access.
Edit: It got figured out. For posterity's sake, you have to run the command from ~/game:cd cd game bin/mux-start
Thenomain explained that the reason for this was because Chime intended for there to be the option to run multiple instances of TMux from the same server.