Selfhosted

61475 readers

1182 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Portabase v1.7.1 - Open source database backup/restore tool (github.com)

submitted 5 months ago* (last edited 5 months ago) by KillianLarcher@lemmy.world to c/selfhosted@lemmy.world

18 comments fedilink hide all child comments

Hi community,

I’m one of the maintainers of Portabase, and this is my first time sharing about it on Lemmy.

Portabase is an open-source platform for database backup and restore.

It’s designed to be simple, reliable, and lightweight, without exposing your databases to public networks. It works via a central server and edge agents (like Portainer), making it perfect for self-hosted or edge environments.

It currently supports 7 databases:

PostgreSQL, MariaDB, MySQL, SQLite, MongoDB, Redis and Valkey

Repository: https://github.com/Portabase/portabase

(we hit 500 stars recently!)

Key features:

Logical backups for PostgreSQL, MySQL, MariaDB, MongoDB, SQLite, Redis, Valkey
Multiple storage backends: local filesystem, S3, Cloudflare R2, Google Drive
Notifications via Discord, Telegram, Slack, webhooks, etc.
Cron-based scheduling with flexible retention strategies
Agent-based architecture for secure, edge-friendly deployments
Ready-to-use Docker Compose setup and Helm Chart

What’s coming next:

Increasing test coverage
Extending database support

I’d love to hear from you: which database would you like to see supported next in Portabase?

you are viewing a single comment's thread
view the rest of the comments

[–] tripping335@piefed.social 4 points 5 months ago (1 children)

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!

[–] KillianLarcher@lemmy.world 3 points 5 months ago

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.