Selfhosted

39435 readers

6 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.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

145

Garage is an open source S3-compatible object storage cluster designed for self hosting (garagehq.deuxfleurs.fr)

submitted 4 months ago* (last edited 4 months ago) by [email protected] to c/[email protected]

28 comments fedilink hide all child comments

Note: I am not affiliated with this project in any way. I think it’s a very promising alternative to things like MinIO and deserves more attention.

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

[–] [email protected] 2 points 4 months ago (2 children)

S3 storage is simpler than running scp -r to a remote node, because you can copy files to S3 in a massively parallel way and scp is generally sequential. It's very easy to protect the API too, as it's just HTTP (and at it, it's also significantly faster than WebDAV).

[–] [email protected] 1 points 4 months ago

Nobody should be using SCP, use rsync.

[–] [email protected] -1 points 4 months ago (1 children)

S3 goes beyond the scope you describe. You disqualify yourself with such statements

[–] [email protected] 2 points 4 months ago (1 children)

Clearly I mean Garage in here when I write "S3." It is significantly easier and faster to run hugo deploy and let it talk to Garage, then to figure out where on a remote node the nginx k8s pod has its data PV mounted and scp files into it. Yes, I could automate that. Yes, I could pin the blog's pod to a single node. Yes, I could use a stable host path for that and use rsync, and I could skip the whole kubernetes insanity for a static html blog.

But I somewhat enjoy poking the tech and yes, using Garage makes deploys faster and it provides me a stable well-known API endpoint for both data transfers and for serving the content, with very little maintenance required to make it work.

[–] [email protected] 1 points 4 months ago (1 children)

I don't follow. S3 is an AWS service that these tools emulate locally by providing the same API. But I'm happy to accept that there's just some misunderstanding 😃

[–] [email protected] 2 points 4 months ago (1 children)

In the context of my comments here, any mention of "S3" means "S3-compatible" in the way that's implemented by Garage. I hope that clarifies it for you.

[–] [email protected] 1 points 3 months ago

Thank you