the fun part about scheduling statuses is that it barely works! and theres no way to check in the web interface 🥰
thank you website boy 🥰 🥰 🥰 🥰
wait it may be my fault scheduled statuses dont work here.
i will investigate
it was my fault, i didnt have a sidekiq queue set up for it
which isnt explained how to do in the documentation, nor does the "dashboard" page in the admin settings explain it either.
very cool. thank you website boy.
AND ALSO the upgrade notes for the 2.7 release didnt explain it either (bc yes i DID look there. BECAUSE WHERE ELSE WOULD THEY BE????)
ugh. im so fucking tired
@compufox how did you need to edit it?
@aescling i had to add an `-q scheduler` to the end of the command.
however, going and looking at the Official Service Units in the github repo they look NOTHING like the ones i have so i dont even fucking know what the difference is tbh.
if you set up your instance after v2.7 was already out im sure you're probably fine
(and if you wanna check, try scheduling a status in tusky or something. if it doesnt get posted then your sidekiq queues are mucked)
@aescling (after checking some more it seems like the systemd units were actually added into the official repo AFTER i had setup my instance. so i guess the ones im running are Unofficial and i guess were like. just listed in the old documentation? idfk)
@aescling i had to edit the sidekiq systemd unit file.
this is not explained anywhere and i had to guess and im lucky i guessed correctly