Hacker News Reader

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.

View on HN

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.

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?

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.

Hard-linking and running concurrent self-updates, sounds like a recipe for disaster.

Reply on news.ycombinator.com