digitalcourage.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Diese Instanz wird betrieben von Digitalcourage e.V. für die Allgemeinheit. Damit wir das nachhaltig tun können, erheben wir einen jährlichen Vorausbeitrag von 1€/Monat per SEPA-Lastschrifteinzug.

Server stats:

812
active users

#selfhosted

62 posts58 participants2 posts today

The 20i FOSS Awards are here! 🎉

If you value free, open source, self-hosted tools, this is a great moment to show your support. Passbolt is running for the Best Open Source Password Manager, and your single click can help us win this year.

But hurry! Voting ends on September 1, 2025.

Vote here 👉 20i.com/foss-awards/category/p

Thank you for your continued support and contribution. ♥️

20i FOSS Awards
20i20i FOSS AwardsThe 20i FOSS Awards are here to celebrate the contribution self-hosted Free Open Source Software makes to our lives every day. The 20i FOSS Awards are your chance to recognise all the hard work that goes in to developing the tools we rely on so much.

Twice now my #GoToSocial instance has gotten "stuck" for lack of a better word, where it refuses to federate out posts until restarted.

It seems to handle inbound federation fine, seems to be able to federate out favorites OK, possibly even DMs, but posts and replies don't go anywhere.

I'm not seeing anything obvious in my logs, just the absence of any activity posting to other instances' /inbox.

Has anyone seen anything like this?

Warum sich mit Cloud-Lösungen herumschlagen, wenn du deine Passwörter auch lokal mit Bitwarden oder KeePass managen kannst? Die richtige Wahl hängt von deinen Bedürfnissen ab, aber ich schwöre auf die Kontrolle über meine Daten im eigenen Keller. #SelfHosted #Datenschutz hobbyblogging.de/bitwarden-vs-

Hobbyblogging · Bitwarden vs Keepass - Meine Erfahrungen - HobbybloggingDer übersichtlichste Vergleich! Bitwarden vs Keepass, welche Software ist besser? Und welche Software solltest du für dich nutzen?

Am I corrupting my data?

lemmy.world/post/34682838

lemmy.worldAm I corrupting my data? - Lemmy.WorldHi everyone, I’ve been working on my homelab for a year and a half now, and I’ve tested several approaches to managing NAS and selfhosted applications. My current setup is an old desktop computer that boots into Proxmox, which has two VMs: - TrueNAS Scale: manages storage, shares and replication. - Debian 12 w/ docker: for all of my selfhosted applications. The applications connect to the TrueNAS’ storage via NFS. I have two identical HDDs as a mirror, another one that has no failsafe (but it’s fine, because the data it contains is non-critical), and an external HDD that I want to use for replication, or some other use I still haven’t decided. Now, the issue is the following. I’ve noticed that TrueNAS complains that the HDDs are Unhealthy and has complained about checksum errors. It also turns out that it can’t run S.M.A.R.T. checks, because instead of using an HBA, I’m directly passing the entire HDDs by ID to the VM. I’ve read recently that it’s discouraged to pass virtualized disks to TrueNAS, as data corruption can occur. And lately I was having trouble with a selfhosted instance of gitea, where data (apparently) got corrupted, and git was throwing errors when you tried to fetch or pull. I don’t know if this is related or not. Now the thing is, I have a very limited budget, so I’m not keen on buying a dedicated HBA just out of a hunch. Is it really needed? I mean, I know I could run TrueNAS directly, instead of using Proxmox, but I’ve found TrueNAS to be a pretty crappy Hypervisor (IMHO) in the past. My main goal is to be able to manage the data that is used in selfhosted applications separately. For example, I want to be able to access Nextcloud’s files, even if the docker instance is broken. But maybe this is just an irrational fear, and I should instead backup the entire docker instances and hope for the best, or maybe I’m just misunderstanding how this works. In any case, I have some data that I want to store and want to reliably archive, and I don’t want the docker apps to have too much control over it. That’s why I went with the current approach. It has also allowed for very granular control. But it’s also a bit more cumbersome, as everytime I want to selfhost a new app, I need to configure datasets, permissions and mounting of NFS shares. Is there a simpler approach to all this? Or should I just buy an HBA and continue with things as they are? If so, which one should I buy (considering a very limited budget)? I’m thankful for any advice you can give and for your time. Have a nice day!
Replied in thread

Correction, see #aside here mastodon.mariobreskic.de/@mari

#aside and #tldr
Running a solo Mastodon instance? Here's how to keep it clean and #gdpr compliant:
– Disable link previews: DISABLE_FETCH_PREVIEWS=true
– Purge old PreviewCards via Rails console
– Avoid federated content
– Self-author everything
– Host locally, anonymize IPs
Respectful publishing, no third-party hosting
#asca #server #mastodon #selfhosted #germany

Mario Breskicʼs MastodonMario Breskic (@mario@mastodon.mariobreskic.de)#aside: the only line that is currently accurate and therefore needed is DISABLE_FETCH_PREVIEWS=true this change supersedes the previous setting, and I will take note of that in the tldr below. #server #asca #mastodon