90
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Mar 2026
90 points (96.9% liked)
Selfhosted
57705 readers
347 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Hi @morethanevil@lemmy.fedifriends.social, We’ve received similar feedback from other users, so we are currently working on it. However, this requires changes to some internal processes, as the system was not initially designed this way. Thanks for the feedback!
Personally, I think going local file config first was the right decision, depending on what the target audience is. For homelab users with one or two databases it may seem like extra work. For professionals or advanced users who like, or even need, to automate using tools like Ansible etc this makes it easier to deploy on larger scale. You can of course allow users to update settings after the fact through the UI while keeping the json file. I have dropped projects in the past due to the exact issue that its only configurable to the UI that makes bulk operations or automation hard or impossible.
I'm currently using shell scripts (pg_dump) and crontabs to back up my databases, so thanks, will check it out!
Thanks for sharing your use case. To be transparent, we didn’t consider automation when we created the local file config, but it’s indeed the perfect use case for this mode of operation. In any case, we’ll keep the current behaviour to avoid breaking changes. This will be introduced as an additional feature.
Okay, will keep an eye on the release notes and give it another try if this is implemented! Anyway it is great that remote backup is supported this is a feature other tools like Databasus don't have.
I’ll keep you updated on this. And yes, remote backups are one of our key differences compared to other systems: the agent-based architecture enables operations across multiple networks without requiring SSH tunnels or exposing databases publicly.