If you ever need an alternative take a look at https://github.com/drakkan/sftpgo

I also had bad luck with nextcloud, so recently I’ve set up SFTPgo and it works rather well and it’s only for files. You can either download and upload the files through the WebUI or you can mount them over the network to your OS.

https://github.com/drakkan/sftpgo

I’d do it like this:

• borg backup

• (optional) borgmatic for easier use, but a diy shell script might suffice

• (optional) https://github.com/Ravinou/borgwarehouse for easier gui based “serverside” setup on each location

• (if you have no way to reach the servers from the internet yet) set up dyndns for each location so you can reach them by domain

• might need to setup portforwarding rules in the router of each location

You can do that with caddy as well.

tldr:

• life, work, family reasons for one of the guys. Nothing negative, he just has no time for the podcast anymore but will show up in their linux podcast from time to time in the future.

But the joke doesn’t work if you are pedantic.

The one we are currently in I assume.

Proxima Centauri is pretty weird with it’s three gravitationally bound suns (Alpha Centauri A and B), who would set up alerrs for that?

/s

What I did is set up a NAS at my parents house, which I can log into as well for near zero cost offsite backups.

And at home I have a couple of local drives with borgbackups.

This keeps backups efficient since you can ask the filesystem to only send the changes instead of going over all the files and figuring out what has changed, so it’s probably a lot faster.

Aaaah!

I use borg with borgmatic. I just back up / (which includes home) and exclude some folders I don’t want (like /mnt or /tmp).

It does the same as you just said.

I have 20 borg snapshots of my nearly full 1tb drive which takes about 400gb of space on my NAS.

I do it at the file structure level, not at the block device level as the article suggests. Why would I want to back it up at the block device level instead?

You misunderstood my question, because what you said is true either way with borg.

The question is, what is the advantage of backing up the whole subvolume “block device” vs just / file structure.

I don’t really understand the advantage of backing up the whole btrfs volume.

I’ve recently looked into https://github.com/firefly-iii/firefly-iii because it has autoimport for my banks API.

It uses mariadb by default and the GUI looked relatively simple.

Whether it fits your needs depend on your budgeting method.

https://github.com/TecharoHQ/anubis/issues/92

note: this is pretty much temporary until we get first class support for Traefik

They seem to be working on a traefik middleware, but in the meantime there is a guide to set it up manually with traefik.

what about a local, encrypted backup

Did they actually selfhost their podcast? Or did they use some 3rd party distributor?

Copied crowdsec reply from the mastodon thread:

tldr: OP misunderstood a bug/usererror as a new limiting policy

Hey Laurence from CrowdSec Support here.

We don’t store logs, so I assume you’re referring to alerts. Based on the screenshot you provided, the most likely reason you’re not seeing any alerts is that they may fall outside the currently selected date range. You can try clicking the magnifying glass icon next to the date picker to remove the filter, which should display all available alerts.

That said, there is a known issue we’re actively fixing—clicking on the date picker may trigger an error. If removing the filter doesn’t work, let me know, and once the fix is live, I’ll be happy to ping you so we can investigate further.

Regarding alert retention, the community tier has always had a limit—either 500 alerts or seven days, whichever comes first. With the new system, we now retain alerts for both the current and previous month, up to 500 per month, effectively doubling the total alert capacity to 1,000. If you’re primarily interested in real-time alerts, keep in mind that the CrowdSec console is designed for alert retention and ease of use, with additional features. Alternatively, for those who prefer a fully customized setup, we provide extensive documentation on integrating CrowdSec with Prometheus and Grafana for self-hosted monitoring.

I understand the frustration, and I appreciate the feedback. However, it’s important to consider that CrowdSec is built and maintained by a dedicated team of around 30 people. While open-source, over 95% of contributions come directly from our team, whether for the hub or various CrowdSec components. Ensuring the long-term sustainability of the project requires balancing free community access with the resources needed to maintain and improve the platform.

Happy to discuss more via email or on this thread, as we truly value feedback and want to ensure every voice is heard across various platforms.

If it’s free - you’re the product

(not applicable to opensource or similar ofc)

Thanks for sharing! Thats good to know info.

Not on topic but do you mind explaining the Pine64 breakage?

I am running a lot of their products and a soquartz cm module broke for me as well, I am hoping the rest will hold on for a long time.