Production ready

[pkking]

Hi @jasonwhite , thanks the awesome project, im curious whether rudolfs production ready or not? Any feature list or roadmap here?

[jasonwhite]

It has been used in production at various places for years now. It is an extremely stable service AFAIK. No telemetry is collected, so I don't have hard data to prove this, but I think it can be inferred by the relatively low number of issues reported.

There are no major outstanding issues preventing usage in production that I know of. If you find any issues, please report them!

[pkking]

We will try to choose rudolfs as our lfs server, seems it fairly lightweight and rust deserve a plus, the only blocker is we need authentication(maybe OIDC or Oauth2), and we are very happy to extend rudolfs if you like :)

[jasonwhite]

@pkking The addition of authentication is welcome as long as it is optional. See also the discussion about authentication in #34 (comment).

[nnWhisperer]

hello, @jasonwhite, why not add a rclone backend, since it handles authentication and more? I think it wouldn't be that hard and plus it would be more stable than one would develop it himself, as it would be standing on the shoulders of the giants. Thanks for the project btw.

[jasonwhite]

@nnWhisperer I think you're talking about authentication with the backend storage service (e.g., AWS S3, etc), which is different from the authentication that the Git LFS client might want to do with Rudolfs.

Nevertheless, an rclone backend isn't a bad idea if it works reliably and integrates well.