Run the Hub

Run the Hub as a service, change its settings, and choose how people sign in.

What you need

• A machine where kndl onboard set up a Hub.

Control the service

kndl hub status    # whether the service runs
kndl hub stop      # stop it until the next start or login
kndl hub start
kndl logs hub -f   # follow its log, ~/.kndl/logs/hub.log

While the Hub is stopped, Sessions keep running on their Runners. The Runners reconnect when it’s back.

Check it’s up

curl http://127.0.0.1:7777/health

{"status":"ok"}

/health needs no sign-in. kndl status checks it for you.

Change its settings

The Hub’s settings are in ~/.kndl/hub.env. Either run kndl onboard again, or edit the file and restart the Hub with it:

kndl hub install

Every setting is in the configuration reference.

Back up hub.env with hub.db

Once a secret is saved, the Hub refuses to start without the same HUB_SECRETS_KEY, and nothing can read the secrets without it.

Choose how people sign in

The Hub needs at least one way to sign in:

• GitHub sign-in, for a team. Set up the GitHub App, then let people in.
• Dev login, for a try on one machine. With KNDL_DEV_LOGIN=1, anyone who reaches the Hub signs in under any name. Onboard offers it for a Hub only this machine reaches, and the Hub refuses to start with it unless HOST and HUB_PUBLIC_URL are both loopback.

With neither, the sign-in page says the Hub has no way to sign in turned on.

Next steps

Reach the Hub from other machinesServe the Hub over HTTPS for your team and Runners elsewhere.

Set up the GitHub AppSign people in with GitHub, and give Sessions their Repo's token.