ALSO: before everything broke, WE SERVED OUR FIRST IMAGE ACROSS OUR NOMADNET SITE. it was a test image of the Become the Thousand Servers project by @sabot.media , which is fitting as it's about NoBlogs going down and what comes next. This means NomadNet blog posts can be more than just words.

Show Post

Upon resolution, a little treat awaited me: BASH chat was loading but the versioning changes involved clearing out docker volumes, a new chat hash was generated and access to old messages was lost. I worked through a few chat fail state options and saw that registrations have increased a lot lately!

Show Post

In the end, all the pip manual mounting folder changes weren't necessary, I was able to mount the Pip install script and install required packages at container start with right permissions, so I went back and cleared out appended PATHs, and also added path for new .env location. Everything's up.

Show Post

The .env file was stored in the served pages folder. The MeshChatX devs changed permissions in the recent update, I think they may have turned off the server folder as a place to store important data and... good. I thought I'd already moved it out of there, tbh. But yeah, forced to improve.

Show Post

When BLOG worked without colors, I decided to pull that function into its specialized function file and completely separate from the CHAT function file. It just had to call the .env file and load the color settings into a usable dict. This should have been simple but it failed. This was the problem

Show Post