-
Notifications
You must be signed in to change notification settings - Fork 423
docs: Deploy with Vercel #2767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Deploy with Vercel #2767
Changes from 3 commits
5a67d9e
614e98d
6bfe118
25fb182
c3312cc
808c575
af7fddc
d018fd9
d038c72
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,66 @@ | ||||||
| # Deploying to Vercel | ||||||
|
|
||||||
| This guide walks you through preparing and deploying a Slack app using Bolt for JavaScript, [Workflow DevKit's](https://useworkflow.dev/) `DurableAgent`, [AI SDK](https://ai-sdk.dev/) tools, the [Nitro](https://nitro.build/) server framework, and [Vercel](https://vercel.com/home). | ||||||
|
|
||||||
| When you’re finished, you’ll have this ⚡️[Slack agent template](https://github.com/vercel-partner-solutions/slack-agent-template) to run, modify, and make your own. | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
| ## Prerequisites | ||||||
|
|
||||||
| First things first, take a few moments to set up the following: | ||||||
|
|
||||||
| * Make sure you have a development environment where you have permission to install apps. You can get a free sandbox with the [Slack developer program](https://api.slack.com/developer-program). | ||||||
|
||||||
| * Make sure you have a development environment where you have permission to install apps. You can get a free sandbox with the [Slack developer program](https://api.slack.com/developer-program). | |
| * Make sure you have a development environment where you have permission to install apps. You can get a free sandbox with the [Slack Developer Program](https://api.slack.com/developer-program). |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Select your provider as the Git Scope and rename the repo if you'd like. Next, click **Create**. | |
| Select your provider as the Git Scope and rename the repo if you'd like. Click **Create**. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Create a new Slack app through [this link](https://api.slack.com/apps?new_app=1), then select **from a manifest**. Next, choose a workspace you have permission to install apps in. Click **Next**, then copy and paste the project manifest code here, replacing the placeholder text in the JSON tab. | |
| Create a new Slack app through [this link](https://api.slack.com/apps?new_app=1), then select **from a manifest**. Next, choose a workspace you have permission to install apps in. Click **Next**, then copy and paste the project manifest code here, replacing the placeholder text in the **JSON** tab. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Now it’ll work through the deployment process and give you updates on what it is doing. Be patient. Deployment is hard work! Once it's finished, you'll see a confirmation screen with a button to **Continue to Dashboard**. Click that button. Here you can see that your app has been deployed! Use this dashboard to keep tabs on build logs, deployment checks and more. | |
| The deployment process will kick off, and you'll receive progress updates. Be patient. Deployment is hard work! Once it's finished, you'll see a confirmation screen with a button to **Continue to Dashboard**. Click that button. Here you can see that your app has been deployed! Use this dashboard to keep tabs on build logs, deployment checks, and more. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👁️🗨️ suggestion(non-blocking): Examples might be nice since paths are never obvious for me and these are different from Bolt defaults:
- Slash Commands URL: https://slack-agent-template-example.vercel.app/api/slack/events
- Event Subscriptions: https://slack-agent-template-example.vercel.app/api/slack/events
- Interactivity Request URL: https://slack-agent-template-example.vercel.app/api/slack/events
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🪬 question: Can we shorten this path?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's a question for @lukegalbraithrussell I feel like we need it for some reason but I don't remember why
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tools/bolt-js/deployments/vercelis a folder path right now. you need this to specify that you want thevercelfile within thevercelfolder.this looks redundant here, but as long as you name the file either 1. the same name as the folder (like you did) or 2.
index, the actual URL will just be "/tools/bolt-js/deployments/vercel"