New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rebuildctl: smarter endpoint detection? #11
Comments
Good point, this has been implimented in the v0.3.0 release! Also note that the default port changed from :8080 to :8484. |
btw, in case your rebuilder is public, feel free to add it to https://wiki.archlinux.org/index.php/Package_rebuilders and/or https://github.com/kpcyrd/ismyarchverifiedyet/blob/master/ismyarchverifiedyet.py :) |
I've listed a status page in the wiki page (only have access to my current hardware for a few more months), though I made the dubious decision to include all of community in my rebuilds and core seems to be stuck after it, so it might be a while before the numbers look right. Is parallelism a thing with rebuilderd? It's running on an 8 core machine and doesn't appear to be taking full advantage of it |
There's a patch that landed recently but isn't released yet: archlinux/archlinux-repro@63b4367 You can try to apply it manually to make use of all cores. Also, nice dashboard! |
The patch has been shipped in |
rebuildctl
should look at/etc/rebuilderd.conf
for finding an endpoint before falling back to the hardcodedhttp://127.0.0.1:8080
. Currently it only checks the-H
arg and a config file in the user's config directoryalso would be nice to have
endpoint
under[http]
in the default/example config for discoverabilityThe text was updated successfully, but these errors were encountered: