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 I had planned on setting this up myself. I never tried using the single instance configuration option for Pinafore, I'd only ever planned on heavily modifying it to deeply integrate with GoToSocial.
For example, Pinofor does not support the concept of modifying your profile, but go to social does. So in order to allow users to do that, I would have to kind of mix and match between two different web applications that link to each other or redirect to each other somehow.
@forestjohnson unfortunately single-instance is not implemented in pinafore, only enafore
I don't love it, but I'm OK with the idea of "you use pinafore for the regular day-to-day posting usage and you log into the completely separate gotosocial settings for the less-common tasks like profile edits" at least in the short term; my goal was more to just get it so you never have to leave your instance domain; like I should be able to navigate to https://hey.hagelb.org/login and have it just work, but I don't think that's viable without significant changes to pinafore
@forestjohnson not that there's anything wrong with adding profile edit support to pinafore; that just seems like a lot to ask when it's missing basic stuff like locals-only posting which would be significantly more beneficial
@technomancy I saw this as more like "providing a builtin ui for gts" or just integrating the two somehow.. I felt like separate server and client webapp would be a needlessly confusing stumbling block if I was trying to get more of my local friends on fedi
