mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,4 Tsd.
aktive Profile

#selfhosted

62 Beiträge60 Beteiligte4 Beiträge heute
Fortgeführter Thread

Well it look a better part of the day and a number of trial and error (as the documentation is a bit outdated in some cases), but I got there in the end!

This was a test instance migration, and it works!

Officially now on Postgres 17.5.

Time to document it all and get some sleep as I will have to redo all this again.

#mysql#postgres#database

Setting up a server for a research team. What should be in my checklist?

sopuli.xyz/post/31947673

sopuli.xyzSetting up a server for a research team. What should be in my checklist? - SopuliI’ve been asked to set up a server for a research team at my university. I’ve already had the practice of setting a server at home, so I have a rough idea of how things should be done. Still, I wish to follow best practices when setting up a server for this use case. Plus I would prefer to avoid too much tinkering for the setup since I’m planning to keep the installation as simple as possible. Following are some rough constraints and considerations for the setup: - Server computer is a Mac Mini (latest model I think?). I’ve been told they would replace macOS with Linux, still I believe I should ready if they don’t (I don’t have experience with macOS at all) - Server will be situated in university and provided a static IP address - Team needs remote access to the server, presumably comfortable with using CLI - I am unlikely to be permitted access to server myself after setup, so it should be ready to be managed by the team - Extra hardware and/or paid software could be arranged but to a limited extent and within reason I don’t think they have really any requirement other than having remote access to the server. I think SSH should suffice, however I was wondering if I could also arrange for backups, GUI server panel etc.

I'm more than half-way through moving all my music from YT Music to my own Funkwhale instance: the classical music is taking longer, because I want to make sure I connect the correct artist/album to the correct MusicBrainz record.

As these are my own copies, I cannot open up my instance to federation, so sharing music will be more difficult than through YT Music, but at least no one will benefit from the clicks/engagement :neocat_winktongue:

Question for other classifical music lovers: where do you buy your digital versions of (new/old) classical music albums?

Backblaze is slow for Nextcloud. Any recommendations for faster s3 compatible storage?

lemmy.today/post/35470403

lemmy.todayBackblaze is slow for Nextcloud. Any recommendations for faster s3 compatible storage? - Lemmy TodayI’ve been using Backblaze B2 as “External Storage” connected to my Nextcloud on a vps, but it seems unreasonably slow. I’ve tried Linode/Akamai, and it seems faster, but it’s more expensive. I’ve heard that Wasabi is fast, but they have weird terms and conditions where you actually have to pay for 3 months of data retention, which makes them sus. I mention s3 compatible, but that’s only because that’s all I’ve known, so if there are other options that are relatively cheap, and are faster than Backblaze, I’m open to it. I have Backblaze connected via the External Storage app in Nextcloud, cuz I’m running Nextcloud AIO in Docker. I know s3 storage can be setup as the main storage, but that requires setting things up manually. AIO is much easier, and I’m not a pro at this stuff. And I’m not sure how much of a performance increase it would even be. Just for reference, I’ve set up a Nextcloud instance for work on a Linode vps at 2 cores and 4GB RAM, using their s3 compatible storage as external storage, and it’s decently fast. My personal Nextcloud is a Racknerd vps at 4 cores and 4GB RAM, with backblaze as external storage, and it’s slower than my work’s instance. (both are AIO) In terms of pricing Backblaze is $6/month for 1TB, while Linode is $10/month for 250GB, and about $20/month for 1TB. Who knows, at the end of the day, I may just have to bite the bullet and pay more for Linode for the faster storage.