garage VS Nebula

Take a look at GarageS3, it's a niceoption for "just an S3 server" for self hosting.

https://garagehq.deuxfleurs.fr/

I use it for self hosting.

Garage (https://garagehq.deuxfleurs.fr/) gets pretty close for object storage. It’s built with mixing high/low latency links and replication between multiple hosts. Unfortunately it’s not really built for end-users, but devs, so there’s no ui or anything like that.

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet.

Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing

I've actually been looking for more open alternatives, but haven't found much.

Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively: https://github.com/scality/cloudserver/issues/4986 (their Docker images on DockerHub were last updated 10 months ago, which is what the homepage links to; blog doesn't seem active since 2019, forums don't have much going on, despite some action on GitHub still)

There was also Garage, but that one is also AGPL v3: https://garagehq.deuxfleurs.fr/

The closest I got was discovering that SeaweedFS has an S3 compatible mode: https://github.com/seaweedfs/seaweedfs

Ah, you should check out Garage (https://garagehq.deuxfleurs.fr/) for a self-hosted, cluster-y API of S3

I'm a big fan of Garage[1], which is a dead-simple S3 drop-in that you can host on your own drives. It's designed for consumer hardware with shitty internet in-between nodes.

[1]:https://garagehq.deuxfleurs.fr/

One more thing we are also proud of: a bunch of our users is using the object storage Garage, this OSS project looks really promising, and we really cherish the OSS for this kind of unexpected combination.

- Another nice comment seen on HN « it seems to be very easy to run, not very IO intensive, and running fine on a single node with modest hardware with >2 billion log rows. It has a really cool dynamic schema feature too.» [9]

Fun fact: at least 4 users are using Garage[10] as the object storage, this OSS project looks really promising and made the HN front page a few months ago[11], we really cherish the OSS for this kind of unexpected combination.

Any feedback positive/negative always greatly appreciated here!

[0] Quickwit repo: https://github.com/quickwit-oss/quickwit

[1] Searching the web under 1000$/month: https://news.ycombinator.com/item?id=27074481

[2] Chitchat gossip library: https://github.com/quickwit-oss/chitchat

[3] Columnar format: https://github.com/quickwit-oss/tantivy/tree/main/columnar

[4] Tantivy library: https://github.com/quickwit-oss/tantivy/

[5] Whichlang library: https://github.com/quickwit-oss/whichlang

[6] GitHub Archive demo in terminal: https://www.youtube.com/watch?v=SNq3bARRlDI

[7] Indexing performance: https://twitter.com/fulmicoton/status/1638016949459488768

[8] https://twitter.com/arnonrgo/status/1645429632303235073?s=20

[9] https://news.ycombinator.com/item?id=35742544

[10] Garage object storage: https://garagehq.deuxfleurs.fr/

[11] https://news.ycombinator.com/item?id=33853539

On the technical side, garage (https://garagehq.deuxfleurs.fr/) does multi master replication by default, so is probably better for this use case. Still with S3 API.

You are looking for garage.

Nebula - Peer-to-peer overlay network. Developed and used internally by Slack. Similar to Tailscale but completely open source. Doesn't use WireGuard. Written in Go.

(I am a Nebula maintainer.) We recently merged support for gVisor-based services, although it's very new, and I don't know of much experimentation that's been done with it yet: https://github.com/slackhq/nebula/pull/965

Nebula, originally from Slack[0].

Wireguard rightly gets a lot of attention, but Nebula is a really simple and easy to deploy mesh network that is often overlooked.

It does lack a management GUI and that stuff is very much DIY.

[0] https://github.com/slackhq/nebula

Fair enough about the android mobile client... My use case only involves meshing linux appliances across various networks so we only need the nebula core binaries which are under MIT license

https://github.com/slackhq/nebula/blob/master/LICENSE

That's not at all confusing with Slack's Nebula. https://github.com/slackhq/nebula

Sounds like a bunch of your pain points are just related to needing an online CA or ICA. But, looking through the Nebula docs I don't know that it supports things like CRL addresses where you could host the CRL, or OCSP responders. Someone got support for an OCSP responder but never submitted a PR with completed code: https://github.com/slackhq/nebula/issues/72

Nebula is a scalable, cross-platform overlay networking tool focused on performance, simplicity, and security. This portable tool is equally adapted for linking a small number of computers or scaling to connect tens of thousands. It integrates encryption, security groups, certificates, and tunneling into a powerful, cohesive connectivity solution. Thanks for the recommendation go to jmeador42.

Replying to my own comment as I can no longer edit it:

The folks over at Slack had an interesting discussion regarding the the "battle of the VPNs" article published by Netmaker I sourced in my parent comment:

https://github.com/slackhq/nebula/discussions/911

Interesting. I thought recognized the logo, apparently seems to be a commercial support offering of https://github.com/slackhq/nebula and they support the "nebula" iOS app. I had been using for nebula/defined in the past.

Nebula: Is super easy to get running. It uses an interesting angle, working on the service and not just the device level. Unfortunately their NAT support seems to be still quite problematic and I am not going to maintain all those forwarded ports manually. There is a PR to support PCP but even if that ever gets applied I am not sure how well that will play with older routers. While it should be battle proven at slack, the community seems to be not that active. It still has the in-house tool that just got released.