So after we’ve extended the virtual cloud server twice, we’re at the max for the current configuration. And with this crazy growth (almost 12k users!!) even now the server is more and more reaching capacity.
Therefore I decided to order a dedicated server. Same one as used for mastodon.world.
So the bad news… we will need some downtime. Hopefully, not too much. I will prepare the new server, copy (rsync) stuff over, stop Lemmy, do last rsync and change the DNS. If all goes well it would take maybe 10 minutes downtime, 30 at most. (With mastodon.world it took 20 minutes, mainly because of a typo :-) )
For those who would like to donate, to cover server costs, you can do so at our OpenCollective or Patreon
Thanks!
Update The server was migrated. It took around 4 minutes downtime. For those who asked, it now uses a dedicated server with a AMD EPYC 7502P 32 Cores “Rome” CPU and 128GB RAM. Should be enough for now.
I will be tuning the database a bit, so that should give some extra seconds of downtime, but just refresh and it’s back. After that I’ll investigate further to the cause of the slow posting. Thanks @[email protected] for assisting with that.
Good idea!
I might be interested in helping, DevOps engineer as well. ☺️
I think this is a great idea as well. I don’t have quite the experience set of @ziiki_transport2 (Primary PSE) but am sure I could pitch in, in some way. Would be a good venue for brainstorming ideas as well(not that you seem to need it ;))
Feel free to ping me as well if something sets up. I currently don’t have the time or personal grit to run a full instance on my own, but I know how to run linux, postgres, mysql, networks and other things. Ansible/Chef mostly as well, some puppet, some salt. Been doing this for 10 years or so on different stacks.
I’d be happy to be part of some “Lemmy-OPs-Support” group, wherever it may be to chime in with experience.