Selfhosted
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.
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!
view the rest of the comments
Buckets have a lot of features that postgres don't. Like mounting via FUSE. And Garage in particular offers some integrations to apps, websited, and so on. I would go with this instead of having a column of byte data in a DB table. The pgsql solution might work in small and simple cases (e.g. storing the user's avatar in a forum) but even so, if I could or had to choose, I wouldn't do it.
Great points.
For isolated projects in the past I've had great success storing things in postgres,. (generally large documents that are relationally tied to other more traditional PG data, in a db driven project) Just saying size and recall have been pretty happy.
As you say the other features are distinguishing.