3 ms·
Hello. Thanks for responding! To be clear. I wanted to use builds.sr.ht on a self hosted server. I opened https://man.sr.ht/builds.sr.ht/configuration.md htt
by shp0ngle 5y ago
Hello.
Thanks for responding!
To be clear. I wanted to use builds.sr.ht on a self hosted server.
I opened https://man.sr.ht/builds.sr.ht/configuration.md https://man.sr.ht/builds.sr.ht/configuration.md and that, at a start, starts with QEMU and KVM. I got too lost in reading that.
Drone, by comparison, is much more easier to set up. (It has some negatives, which I won't get into here. But it is much more easy to set up.)
https://docs.drone.io/server/provider/github/ https://docs.drone.io/server/provider/github/
https://docs.drone.io/runner/docker/installation/linux/ https://docs.drone.io/runner/docker/installation/linux/
Maybe I opened a wrong markdown file?
- ddevault 5y agoOh, yeah, it is definitely requires some effort to set up sr.ht for self-hosted installs, though many have managed it. I think NixOS is working on making it easier. In any case, will address this following 1.0, when development will slow down a bit. This is indeed a known defect. However, I think there is some validity to the idea that we shouldn't make every system as simple as possible, especially given that this one has security implications. I think you should be willing to understand how something works and not to reject anything that isn't plug-and-play. Let's meet somewhere in the middle after the 1.0 release, alright? :)
- shp0ngle 5y agoThanks. I got into issue "drone is acting weird because of issue X, how easy would be to fix it vs. migrate to builds.sr.ht?" and it turned out, fixing it was much faster (in the end it was dumb problem with docker networks) than migrating to a whole new system.