buildout Slack integration

This commit is contained in:
KS Jannette
2026-08-22 00:52:55 -04:00
parent b607ee9121
commit 17746e9268

View File

@@ -140,7 +140,7 @@ DATABASE_URL=postgresql://<user>:<password>@localhost:5432/kongruity
EOF EOF
``` ```
Replace placeholder values with your actual keys and database credentials. Replace placeholder values with your keys and database credentials.
#### Integration variables #### Integration variables
@@ -179,7 +179,7 @@ EOF
`SLACK_SIGNING_SECRET` is already in the integration variables above. There is no OAuth flow here on purpose: a single workspace reading credentials from the environment is far less machinery than an install dance, and the OAuth endpoints in the provider registry stay unused until multi-workspace support is actually needed. `SLACK_SIGNING_SECRET` is already in the integration variables above. There is no OAuth flow here on purpose: a single workspace reading credentials from the environment is far less machinery than an install dance, and the OAuth endpoints in the provider registry stay unused until multi-workspace support is actually needed.
### 2. Expose your local backend ### 2. Expose backend
Slack only delivers to a public HTTPS URL, so a tunnel is required for local development. Slack only delivers to a public HTTPS URL, so a tunnel is required for local development.