this post was submitted on 05 Jul 2023
142 points (98.0% liked)

Mbin Blog Updates

7 readers
1 users here now

Blog updates for Mbin (fork of /kbin). Upcoming features, issues or anything else related Mbin or the fediverse.

Just follow this magazine to keep yourself up-to-date!

founded 2 years ago
MODERATORS
142
Kbin.social upgrade (kbin.melroy.org)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

Currently, the kbin.social instance has planned maintenance. They are busy upgrading the infrastructure to Kubernetes, using Docker containers. They said it shouldn't take much longer than 1 hour downtime in total (if everything goes fine).

The migration will help to dynamically scale the instance, to remove the growing pains. And hopefully increase the availability (uptime) as well.

Soon additional setup configurations, best server practices and ansible playbooks will be shared with the community.

In the meanwhile you can of course use other instances (I bet you are reading this message right now from another instance).

you are viewing a single comment's thread
view the rest of the comments
[–] jcb2016 1 points 1 year ago* (last edited 1 year ago) (1 children)
[–] [email protected] 3 points 1 year ago (2 children)
[–] MCForTheBest 2 points 1 year ago (1 children)

From what I've seen, when it went back up for a few minutes, they changed the interface, the thumbnails were on the left side and it now shows your profile picture next to your username in the upper right. Those were the more obvious changes, of course.

I don't know if those changes stay permanent but it looked really nice! (That's just as an FYI for everyone who didn't see the site go back up)

[–] [email protected] 2 points 1 year ago

These are only the cosmetic changes you see. Kbin.social was running a quite old version indeed. I try to keep my instance up-to-date every day, running the latest changes from the develop branch.

That being said, there are a lot of other changes you are not aware of. These can be database changes, performance improvements, backend features. Or any other code change, bug fix or improvement, which isn't always obvious to the end-user.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

It's up again?

EDIT: But I notice some image cache issues.