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
1.5 KiB
title, description, nav, order, category
| title | description | nav | order | category |
|---|---|---|---|---|
| Discord for Hub | Create the Discord application your Hub uses and connect a server. | Discord app | 77 | Hub |
Discord for Hub
Hub connects out to Discord through the gateway. Discord does not send event webhooks to Hub, so the bot does not need a public inbound endpoint.
Open Apps → Discord. Hub gives you the redirect URL and the exact steps to create the application, enable its bot, and copy the Application ID, Client Secret, and Bot token.
Under Bot → Privileged Gateway Intents, enable Message Content Intent. Without it, the bot receives empty messages and no trigger can match. Server Members Intent is not needed.
Paste the credentials into Hub and choose Verify and save. Then choose Add to a Discord server and authorize the server. Start the authorization from Hub so the server is bound to the active Hub organization.
One Discord application and gateway connection serves every organization and server connected to this Hub. Keep the Hub process running; events that arrive while it is stopped are missed.
Now write a Discord trigger.
Configure from environment
Deployments that keep app secrets outside Hub can set:
DISCORD_CLIENT_ID=
DISCORD_CLIENT_SECRET=
DISCORD_BOT_TOKEN=
DISCORD_CLIENT_ID is the Application ID shown under General Information. Environment configuration takes precedence over a saved Discord application and appears as Managed by environment under Apps.