@vahnj hey is there a way to know what glitchsoc revision awoo is running against?
@cat like which commit?
i pull from the glitch.social master when major fixes on glitch-specific features happen, or if the main masto branch pushes a release
gimme a sec and i'll show you what commit
@vahnj yeah, just trying to work out if a thing is custom or something glitchsoc itself does
@cat our code's hosted at https://github.com/vahnj/mastodon if you wanna look there
@vahnj I can’t get this running because pghero can’t find “Mime” when it’s trying to populate the database
god fucking damn I hate ruby so much
@vahnj so I can’t get the code running, and I can’t find the code for the thing I’m looking at, and I can’t have access to a thing running vanilla glitchsoc
so how the FUCK am I meant to send them a well-considered issue about this
@cat how are you trying to get it going?
i usually just set up rbenv and nvm with the proper versions, run the associated installs for ruby and npm/node, then follow the instructions for setting up over at https://github.com/tootsuite/documentation
i'm kinda handwaving i know it's more complex than that but that's about how it boils down
@vahnj yeah I followed https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Development-guide.md exactly but `bundle exec rails db:setup` fails with `NameError: Uninitialized constant Mime` somewhere in ActiveSupport
@cat oh right, there's a development guide
i feel dirty because i have a test instance rather than trying to run things locally
@cat looks like it might actually be "test", instead of "development"
@cat no i was right the first time. i wonder if development is just the default
@vahnj nope same issue with that setting
@cat ugh google searches are telling me it's potentially related to a lib issue
i wish i had more time to help you figure this out
@vahnj oh it might be
because it’s wanting a pghero that’s like a year old (1.7) and I already have a “current” one (2.1) thanks to work
and rbenv doesn’t isolate project rubies aaaaaaaaaa
@cat uuuugh why can't everything work like pip and virtualenv
@cat try `RAILS_ENV=development bundle exec rails db:setup`