Retro social administration
Also, our sidekiq queue is a little backlogged becuase it's retrying a bunch of jobs that failed last night while we were broken.
For users, this means stuff will be a little sluggish for a few hours. It'll start working normally after that.
Now, to write a custom theme...
Retro social administration
After a few false starts, we are up to 3.0.1 and in a better place to roll new updates out as they come.
I'll be moving us to daily backups today, and setting up a brutaldon instance soon!
We have elastic search! It might be resource constrained, but it exists. I'll be monitoring and balancing.
Big thanks to @danhunsaker for all his help!! Send them some good feels!
This is a combo #RetroHardware and #HardwareHacking project: Running a 1980s monochrome CRT with a 6845 chip (found in a lot of Z80 and 6502 chip based machines of the time) and an Arduino Uno
It sticks everything in a folder, though, and I don't love that.
I'll make some updates.
Anyway, trade radio will be online soon.
retro.social should be back soon.
My tilde site will be up soon, although I lost a bunch of content, which makes me sad but whatever.
Here's a picture of one of my XT clones that I recently got working.
It's a sharp pc-7100, and it has a dead HDD, but it is beautiful.
I'm joking, of course, but in all seriousness: If any other #InstanceAdmins want to help me out with this, I'd be really appreciative (and willing to compensate financially.)
This week especially, I'm just not going to have the time to get things cleaned up and repaired the way that I want. (I'll explain why in another post, under a couple of CWs.)
Fixing this is pretty simple. I could just blow out everything I have, take a fresh database dump, and do it all again, but install it the right way this time.
I'm just not sure when I'm going to have the time to do it.
death; sad; travel; family; work; stress;
So I've got the fallout from mom's passing, plus the fact that my mastodon server is broken *and* another server I run went down with hardware problems, and work is very busy.
I just don't have much time to think this week.
So if someone wants to step in and help me get retro healthy again, I'd really appreciate it, and I'll gladly pay for your time.
death; sad; travel; family; work; stress;
I have to wrap up a couple of projects at my job before I go.
Normally, in this kind of a situation I would just blow those projects off.
But here's the thing: I was already planning on going to GA this week. I have just over a full week trip planned, and me being able to stay gone that long is contingent on getting stuff done before I go.
death; sad; travel; family; work; stress;
I can probably fix this without too much effort. I just need to take the time to do it.
And time isn't something I have a lot of this week.
My mom died yesterday. She was 49 years and 11 months old. They're not doing a viewing or a service, but there's a bunch of stuff I have to do in Georgia as a result, and Georgia is 600 miles away.
And I'm *busy* at work.
First I tried to go straight to 2.8 (this doesn't work, because the DB can't migrate over that many versions.) I did this following the current install guide.
Then, I decided I'd just install the next version after the one we're on, and migrate the DB then (the right way, right?)
Except I decided to do it in place, and check out the version we're going to.
This doesn't work, because the install guide installs a bunch of pre-reqs for later versions, so I've got pre-req mismatches
Details of our situation:
We're running in Docker. Well, specifically, we're running via Nanobox, and that's at least part of the problem.
Sidkiq is not working.
I have a database backup, and our secrets saved.
We're a couple of versions behind, which is what is causing the biggest portion of our problems.
I have another server, and I was going to migrate everything over. Here's where I fucked up:
I'm joking, of course, but in all seriousness: If any other #InstanceAdmins want to help me out with this, I'd be really appreciative (and willing to compensate financially.)
This week especially, I'm just not going to have the time to get things cleaned up and repaired the way that I want. (I'll explain why in another post, under a couple of CWs.)
(if anyone is curious about how/why I fucked up today, I'll be happy to explain it all to you, on the condition that you help me fix it. :-P )
Alright, things are still broken, but I mostly know why and I have a plan to fix them.
It's just 2AM again, so Retro is going to be dead at least until tomorrow.
One of the bits that I'm excited about, if I can get everything else working tonight, is a new database backup strategy.
If everything goes according to plan, the server will be much easier to maintain in the future.
Alt of ajroach42@mastodon.social
Just here for the florps.