Re:Sourcehut's Year in Alpha
by yjftsjthsd-h on Friday November 15, 2019 @12:21PM
(#21546671)
One angle that I'm not sure sourcehut even intends to address but am curious how to idiomatically handle: artifacts. Right now I can (and do) host code in (git|hg).sr.ht and make sure that it compiles with builds.sr.ht, but there isn't an artifacts.sr.ht (and I understand not intending there to be, unless you charge by use and maybe not even then), but it would be nice if I could have the full CI/CD pipeline on sourcehut, including building and publishing final packages. So is the right way to do this to post artifacts to a third-party store (ex. S3) and just stick required authentication in using the secrets support in builds.sr.ht?
[ Parent
| on HN ]
This is actually planned to be supported soon. I recently provisioned a 64TB NAS for the purpose of object storage. It'll support things like release binaries, builds.sr.ht artifacts & build caches, a github pages-esque feature, etc. I just need to figure out how the heck Ceph works.
Another way of doing it is to run minio federation , might be a worthy alternative to Ceph, which has a reputation of hard to run product.
I've looked into minio, but I think Ceph offers more of the features that I want. I don't just want S3 object storage - filesystem and block device options are both things that Sourcehut would take advantage of from Ceph, too.
I thought ceph had a reputation of easy to run, at least compared to it's rivals in the distributed storage space. (gluster, lustre, et al)
Sure, but when you’re running a service you kind of want to know what you’re running. I’m sure Drew is able to figure out the beginning rather easy, but you kind of want to be able to see pitfalls and common misconfigurations etc. It takes a bit of tinkering :).