Mohamed BoudraandGitHub
9163aed3f1
* docs(hub): drop the manual auth secret from self-hosting setup Hub generates its authentication secret on first start and stores it in the database it is already using, so self-hosters no longer run openssl or carry PASEO_HUB_AUTH_SECRET between restarts. The variable stays as an override for deployments that must supply the secret from a platform secret store; Hub uses it without persisting it, so removing it resumes the stored value. Also corrects a claim that predates this change: rotating the secret does not invalidate execution credentials already issued. Hub verifies those against persisted hashes rather than the secret, so only browser sessions end. Documentation companion to https://github.com/getpaseo/hub/pull/50. * docs(hub): lead with the local guided setup * docs(hub): document XDG data directory * docs: make Hub self-hosting the quickstart
795 B
795 B
title, description, nav, order, category
| title | description | nav | order | category |
|---|---|---|---|---|
| Hosted Hub | Sign in to the managed Paseo Hub or self-host the same service. | Hosted | 73 | Hub |
Hosted Hub
Paseo Hub is the managed service. It is not generally available yet: existing accounts can sign in, but new account registration is closed.
To start now, run Hub yourself. Projects, configuration, triggers, daemons, and activity use the same model in both forms. The managed service owns its GitHub App, Slack app, and Discord application; a self-hosted Hub uses apps you create and control.
For the hosted release, join the Paseo Discord and watch the #paseo-hub channel. The release will be announced there; you do not need to message anyone directly.