Hi Paul,
Thank you for the response, I am glad to know you have enough power to run the project.
> I assume this server is a regular architecture. If it's idle otherwise,
has a stable IP and if we could control it, we could add it without too
much effort. If your doing other stuff on it, I rather decline this offer.
Yes, I run multiple infrastructures and projects on it but it has still some available power.
> Now, rasberrypi. What exactly did you have in mind? Do those run native
Debian nowadays, or were you more interested in adding this worker to
our infrastructure and not targeting Debian? The latter we could do, but
I assume you understand it's not our focus right now as the release of
bullseye is nearing an important phase. rasberrypi is armhf, right?
We're currently running armhf on a arm64 host, so we could add it to the
pool if it runs native Debian. (IP, control, same applies as above). I'm
not good at computer specs, so I have not much clue if this would make
sense or not.
Quite a while I did not use a RPI but they are armhf or arm64 as far as I know, I was thinking to turn one into a worker.
But I can not allocate an IP for it, and was thinking that you could send jobs to workers connected to a pool :/ (just like GitHub actions runners work)
I understand the focus is now on the release but let me know if one-day you need some kind of help.
But sure I understand that my free help will not be necessary if the project just can buy machines, ram, etc..
William