has anyone had luck setting up a single-serving pinafore/semaphore/enafore on a gotosocial server before?
it looks like pinafore kinda supports it according to https://github.com/nolanlawson/pinafore/issues/1287
enafore seems to have explicit support for setting it to be locked into a single instance: https://github.com/enafore/enafore/issues/35 which looks great!
however, enafore deleted all the installation instructions out of their readme, (wat) and the instructions for how to install from pinafore don't work for enafore for npm-related reasons I am really not keen on deciphering
gotosocial does allow you to drop a bunch of static files into the web/assets directory which get served up for requests, which is great! but it looks like if you try to put pinafore there, it won't load because pinafore seems to assume it's running at the root of the domain and doesn't work when relocated to a different path so even if I got enafore's npmshit figured out, I don't think it would actually work?
I had already broken my decade+ moratorium on having npm stuff installed on any machine I run when I got the gotosocial stuff packaged a few days ago, which like ... it was for a good cause; fine, I don't like it but you do what you gotta do
but that was relatively painless (three simple commands copied out of the install instructions that somehow actually worked on the first try which I did not expect) and this is ... well, my instinct is telling me it's one of those problems that looks tantalizingly close so you hunker down but then three days later you come to your senses face down in a muddy ditch and realize it's time to give up and go home
@technomancy If you ever find anyone who has done this or deployed it or packaged it in some way, let me know because I'm curious about it.
