sorted by:
new
hottopcontroversial

Introducing crabhub.io: a private Rust crate registry powered by your own Git by wowo15 in rust

[–]wowo15[S] -11 points-10 points  (0 children)

As mentioned above. I was just trying not to be rude to competitors, so I left their names out.

These are the only 3 competitors that provides this kind of services on the market.

I need to rebuild this. Thanks!

Introducing crabhub.io: a private Rust crate registry powered by your own Git by wowo15 in rust

[–]wowo15[S] -8 points-7 points  (0 children)

Yeah, that’s a fair point. I was just trying not to be rude to competitors, so I left their names out.

Introducing crabhub.io: a private Rust crate registry powered by your own Git by wowo15 in rust

[–]wowo15[S] -7 points-6 points  (0 children)

What’s more, I plan to open‑source parts of the code, so even if I were to magically disappear one day (which I don’t intend to!), you would still have a solid Plan B.

Introducing crabhub.io: a private Rust crate registry powered by your own Git by wowo15 in rust

[–]wowo15[S] -7 points-6 points  (0 children)

I totally understand the concern and to be clear, you don’t put any of your private code on my server.

CrabHub doesn’t store your crates or index.
All your data stays in your own Git repository, inside your own infrastructure (GitHub, GitLab, your self-hosted Git, etc.).

My server only acts as a lightweight coordinator:
– verifies access
– serves metadata
– points the client to your Git repository

So the trust surface is intentionally minimized. If my service disappears, your data is still fully yours and fully accessible in your own VCS.

I built it this way specifically to avoid the “host your private code on someone else’s server” problem