Do even self hosters need to pay for runners?

[dkebler]

I was looking around for an alternative to cronicle and so I am evaluating semaphoreui. I totally like that is a single GO binary. But it seems one must pay for "runners" (i.e. to run scheduled code on other machines) even if you are self hosting?

I would say for most of us without runners semaphoreui is useless since we need to coordinate tasks across mutliple machines like I do now with cronicle in my home lab.

Can someone confirm this? If so I will stop evaluating and move on. And if so I suggest that the documentation/website be more explicit up front that community members will ONLY be able to use it per machine.

(I suppose if the runner code is not missing from the source then one could build their own version with it enabled?)

[fiftin]

Runners available in open source version for free.

[dkebler]

I am using

2.11.2-0e9490c-1735214524 on arch which I downloaded from the assets of latest release here at this repo (amd64 tarball)
https://github.com/semaphoreui/semaphore/releases/download/v2.11.2/semaphore_2.11.2_linux_amd64.tar.gz

does that include adding via the web UI or just via command line?

if via the command line I am unable to do that. See this issue.

#2673

My experience so far is I can't register a runner and there is that glaring "pro" notice in the UI which made me believe that this feature is disabled in the assest I downloaded.

[fiftin]

It is project specific runners. We need paid users to develop the software, so it is ad of Pro version.

You can use global runners for free.

[dkebler]

@fiftin runners is not a menu choice for 2.11.2 I see you have a "saas" version so to be apples and apples you'd have to be running the release I downloaded from github.

I see you are one of the contributors so maybe maybe some decision you are unaware was made recently to remove runners from the github releases and force self-hosted users to buy a self-hosted subscription. If I look now the website https://semaphoreui.com/pricing/ to access running self-hosted you must pay

For grins I downloaded the pro version and installed a trail license and runners are available.

I don't mean to get something for nothing and I am happy to make a donation to projects that really makes a difference to me especially management/time wise. What I don't do is buy subscriptions (don't we all have enough of those). Maybe you all can consider a "lifetime" subscription (i.e. a one time payment).

I guess I just have to drop my evaluation and move on :(. Thx for your replies.

[dkebler]

Maybe I am wrong. Seems maybe one can do still connect to runners in the open source server

#2673 (comment)

[dkebler]

https://docs.semaphoreui.com/administration-guide/runners/
echo REGISTRATION_TOKEN | semaphore runner register --stdin-registration-token --config /path/to/your/config/file.json

echo sometoken | semaphore12 runner register --stdin-registration-token --config $PWD/config.json
Loading config
Validating config
panic: runner token file required

goroutine 1 [running]:
github.com/semaphoreui/semaphore/cli/cmd.registerRunner()
	/home/runner/work/semaphore/semaphore/cli/cmd/runner_register.go:41 +0xce
github.com/semaphoreui/semaphore/cli/cmd.init.func5(0xc0001b1300?, {0xcde222?, 0x4?, 0xcde226?})
	/home/runner/work/semaphore/semaphore/cli/cmd/runner_register.go:49 +0xf
github.com/spf13/cobra.(*Command).execute(0x1fea840, {0xc0001c9680, 0x3, 0x3})
	/home/runner/work/semaphore/semaphore/vendor/github.com/spf13/cobra/command.go:989 +0xa91
github.com/spf13/cobra.(*Command).ExecuteC(0x1fea280)
	/home/runner/work/semaphore/semaphore/vendor/github.com/spf13/cobra/command.go:1117 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
	/home/runner/work/semaphore/semaphore/vendor/github.com/spf13/cobra/command.go:1041
github.com/semaphoreui/semaphore/cli/cmd.Execute()
	/home/runner/work/semaphore/semaphore/cli/cmd/root.go:56 +0xc5
main.main()
	/home/runner/work/semaphore/semaphore/cli/main.go:8 +0xf

[fiftin]

It looks like a bug.

[dkebler]

I got it figured out.

before I cloud see/use runners I had to add this to config.json

"use_remote_runner": true,