Skip to content

Commit d1372cc

Browse files
docs: update install instructions and manifest update details (#122)
Syncing docs across source repos Co-authored-by: haleychaas <[email protected]>
1 parent d539f0e commit d1372cc

File tree

3 files changed

+13
-1
lines changed

3 files changed

+13
-1
lines changed

docs/guides/installing-the-slack-cli-for-mac-and-linux.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,8 @@ Solution: Sudo actions within the scripts were removed so as not to create any s
8686
</TabItem>
8787
<TabItem value="Manual" label="Manual Installation">
8888

89+
Manual installation allows you to omit the Deno installation if you don't need it. Deno is needed if you are creating [workflow apps](https://docs.slack.dev/workflows). If you intend to solely use the CLI for Bolt apps, you do not need Deno. If you forgo the Deno installation, skip to step 3.
90+
8991
**1\. Download and install [Deno](https://deno.land).** Refer to [Install Deno](/deno-slack-sdk/guides/installing-deno) for more details.
9092

9193
**2\. Verify that Deno is installed and in your path.**

docs/guides/installing-the-slack-cli-for-windows.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,8 @@ Solution: For the installer to work correctly, your PowerShell session's [langua
108108
</TabItem>
109109
<TabItem value="Manual" label="Manual Installation">
110110

111+
Manual installation allows you to omit the Deno installation if you don't need it. Deno is needed if you are creating [workflow apps](https://docs.slack.dev/workflows). If you intend to solely use the CLI for Bolt apps, you do not need Deno. If you forgo the Deno installation, skip to step 3.
112+
111113
**1\. Download and install [Deno](https://deno.land).** Refer to [Install Deno](/deno-slack-sdk/guides/installing-deno) for more details.
112114

113115
**2\. Verify that Deno is installed and in your path.**

docs/guides/using-slack-cli-with-bolt-frameworks.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,4 +46,12 @@ To run your new app, use the `slack run` command with the experiment flag as fol
4646
slack run
4747
```
4848

49-
You'll be prompted to choose your team/workspace, and then your app should let you know that it's up and running. 🎉
49+
You'll be prompted to choose your team/workspace, and then your app should let you know that it's up and running. 🎉
50+
51+
## App manifest
52+
53+
The Slack app manifest is the configuration of the app. The `manifest.json` file included with selected templates and samples reflects the features and permissions of your app. When you create an app with the CLI, the corresponding app and matching manifest can be found on [app settings](https://api.slack.com/apps).
54+
55+
For Bolt apps created through the CLI, by default, the manifest source set in the `config.json` file is `remote`. This means that the manifest in your [app settings](https://api.slack.com/apps) is the source of truth. To modify the manifest (add new features, scopes, etc.), do so in the app settings. If you change the `config.json` to reflect a `local` manifest source and modify the local `manifest.json` file, the CLI will ask for confirmation before overriding the settings upstream on reinstall (run). This prompt appears if the app manifest on app settings differs from a known state saved in `.slack/cache`. There is not currently a dedicated manifest update command.
56+
57+
In contrast, Deno apps created with the CLI have the manifest source configuration of `local` because those apps are not managed in the [app settings page](https://api.slack.com/apps).

0 commit comments

Comments
 (0)