anyhow, I'm bummed about not getting glitch social to work, but I'm glad the site appears to be running well on the new server.
@jerry Bummer. That's what we use and it's great.
@estoricru It looks to be a known issue - I am not adept enough in github-fu to check out a version of the source from before the bug was introduced.
@TheGibson @estoricru that’s effectively what I did, but the precompile fails, and then its error 500 city. There appears to be an open issue opened a few days ago with the same problem. I am not sure how to checkout the 2.9.2 version of glitch, since they don’t gave tagged releases, just the master branch
The instructions I followed (https://docs.joinmastodon.org/administration/installation/) had me install ruby 2.6.1, which could be the issue.
@seven @TheGibson @estoricru I did - after I couldn't get glitch working, I tried reverting the source back to straight mastodon, recompiled and started up - things kind of worked, but it wouldn't let me toot and a few other odd problems I (possible incorrectly) attributed to the database schema updates.
@jerry @thegibson @estoricru make sure you follow this bit for glitch after you have a working masto proper. https://glitch-soc.github.io/docs/ Pay special attention to clearing the ruby cache. I was definitely having issues with 2.6.1 ruby with glitch for a little bit getting compiles off correctly, when I chased down the problems, it became fairly obvious they are using a slightly newer ruby for building (odds are similar to my setup at this point).
At least I know what isn't the problem.
The ruby cache clearing in the glitch docs indicate that it runs last - did you need to do that earlier?
A Mastodon instance for info/cyber security-minded people.