You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: extensions/chat-with-content/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ As a Posit Connect administrator, you need to configure the environment for this
21
21
22
22
1.**Publish the Extension**: Publish this application to Posit Connect.
23
23
24
-
2.**Configure Environment Variables**: In the "Vars" pane of the content settings, you need to set environment variables to configure the LLM provider. This extension uses the `chatlas` library, which supports various LLM providers like OpenAI, Azure OpenAI, Google Gemini, Anthropic, and Anthropic on AWS Bedrock.
24
+
2.**Configure Environment Variables**: In the content settings, set the following environment variables to configure the LLM provider. This extension uses the `chatlas` library, which supports various LLM providers like OpenAI, Azure OpenAI, Google Gemini, Anthropic, and Anthropic on AWS Bedrock.
25
25
26
26
Set `CHATLAS_CHAT_PROVIDER_MODEL` to specify the provider and model in the format `provider/model`. You also need to provide the API key for the chosen service.
27
27
@@ -52,7 +52,7 @@ As a Posit Connect administrator, you need to configure the environment for this
52
52
53
53
The application uses the [botocore](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/credentials.html) credential chain for AWS authentication. If the Connect server is running on an EC2 instance with an IAM role that grants access to Bedrock, credentials are automatically detected and no configuration is needed. In this case, the application uses the `us.anthropic.claude-sonnet-4-20250514-v1:0` model by default.
54
54
55
-
To use Bedrock without an IAM role, set the standard AWS environment variables in the "Vars" pane:
55
+
To use Bedrock without an IAM role, set the following environment variables in the content settings:
56
56
57
57
-`AWS_ACCESS_KEY_ID`: `<your-aws-access-key>`
58
58
-`AWS_SECRET_ACCESS_KEY`: `<your-aws-secret-key>` (Set this as a secret)
@@ -61,7 +61,7 @@ As a Posit Connect administrator, you need to configure the environment for this
61
61
62
62
For more details on supported providers and their arguments, see the [chatlas documentation](https://posit-dev.github.io/chatlas/reference/ChatAuto.html).
63
63
64
-
3.**Enable Visitor API Key Integration**: This extension requires access to the Connect API on behalf of the visiting user to list their available content. In the "Access" pane of the content settings, add a "Connect Visitor API Key" integration.
64
+
3.**Enable Visitor API Key Integration**: This extension requires access to the Connect API on behalf of the visiting user to list their available content. In the content settings, add a "Connect Visitor API Key" integration.
"This app requires the <code>CHATLAS_CHAT_PROVIDER_MODEL</code> environment variable to be "
129
-
"set along with an LLM API Key in the content access panel. Please set them in your environment before running the app. "
129
+
"set along with an LLM API Key in the content settings. Please set them in your environment before running the app. "
130
130
'See the <a href="https://posit-dev.github.io/chatlas/reference/ChatAuto.html" class="setup-link" target="_blank" rel="noopener">documentation</a> for more details on which arguments can be set for each Chatlas provider.'
f"The URL should contain a GUID like: <code>1d97c1ff-e56c-4074-906f-cb3557685b75</code><br><br>"
154
148
f"The URL provided is: <a href=\"{input_string}\" target=\"_blank\" rel=\"noopener noreferrer\">{input_string}</a><br><br>"
155
149
f"Please update your environment variable with a valid a URL containing a GUID.<br><br>"
156
-
f"Or copy the GUID from the bottom of the Info tab. See the <a href=\"https://docs.posit.co/connect/user/content-settings/\" target=\"_blank\" rel=\"noopener noreferrer\">Connect Content Settings User Guide</a> instructions for more information.<br><br>"
150
+
f"Or copy the GUID from the content settings. See the <a href=\"https://docs.posit.co/connect/user/content-settings/\" target=\"_blank\" rel=\"noopener noreferrer\">Connect Content Settings User Guide</a> for more information.<br><br>"
f"The provided value was: <code>{input_string}</code><br><br>"
165
159
f"Please update your environment variable with a valid GUID or a URL containing a GUID.<br><br>"
166
-
f"The GUID can be found at the bottom of the Info tab. See the <a href=\"https://docs.posit.co/connect/user/content-settings/\" target=\"_blank\" rel=\"noopener noreferrer\">Connect Content Settings User Guide</a> instructions for more information.<br><br>"
160
+
f"The GUID can be found in the content settings. See the <a href=\"https://docs.posit.co/connect/user/content-settings/\" target=\"_blank\" rel=\"noopener noreferrer\">Connect Content Settings User Guide</a> for more information.<br><br>"
Copy file name to clipboardExpand all lines: extensions/simple-shiny-chat-with-mcp/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Set the appropriate API key for your chosen provider:
40
40
1.**Minimum Connect Version**: 2025.04.0 or later
41
41
2.**Minimum Python Version**: 3.10 or later
42
42
3.**OAuth Integrations**: Must be enabled on your Connect server
43
-
4.**Connect Visitor API Key**: This extension requires access to the Connect API on behalf of the visiting user to list their available content. In the "Access" pane of the content settings, add a "Connect Visitor API Key" integration.
43
+
4.**Connect Visitor API Key**: This extension requires access to the Connect API on behalf of the visiting user to list their available content. In the content settings, add a "Connect Visitor API Key" integration.
44
44
45
45
## Setup Examples
46
46
@@ -79,7 +79,7 @@ Deploy this extension to your Connect server with the required environment varia
79
79
80
80
### 2. Configure Access
81
81
In the Connect dashboard:
82
-
1.Navigate to the content access panel
82
+
1.Open the content settings
83
83
2. Add a "Connect Visitor API Key" integration
84
84
3. This enables the chat application to authenticate with MCP servers
0 commit comments