Re:Pricing Changes for GitHub Actions
by pxc on Tuesday December 16, 2025 @04:20PM
(#46294656)
And if you want any concurrency at all, you need 1 runner registration per concurrent job. And each runner needs its own user. And each runner requires a full and separate copy of the runner software, which is large (hundreds of megs) and self-updates.
[ Parent
| on HN ]
Re:Pricing Changes for GitHub Actions
by paulddraper on Tuesday December 16, 2025 @05:45PM
(#46295726)
You don't need your own user.
The rest is correct. (Though you can hardlink the installation.) And you can disable self-update, though it does it by default.
Re:Pricing Changes for GitHub Actions
by gheltllck on Tuesday December 16, 2025 @09:32PM
(#46297557)
Hard-linking and running concurrent self-updates, sounds like a recipe for disaster.
Ah right, I've forgotten because I'm using a multi-user strategy and a patched version of the runner at this point anyway. The config directory for each runner is normally based on its install path (insane), something like that?
Re:Pricing Changes for GitHub Actions
by paulddraper on Friday December 19, 2025 @04:47PM
(#46331328)
The config directory based on the install directory, yes.
To be fair, running multiple copies of a service isn't that common.
E.g. if you wanted to run multiple copies of PostgreSQL you can't just do a vanilla install.