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
Baserow supports multiple AI providers for generative AI features and the AI assistant. The embeddings service powers semantic search for the AI assistant's documentation lookup feature. For more documentation check the [Baserow AI documentation](/docs/installation/ai-assistant.md).
98
+
99
+
### Enable AI Assistant
100
+
101
+
To enable the AI assistant, you need to configure the LLM model and provide the necessary API keys for the chosen provider.
102
+
103
+
```yaml
104
+
global:
105
+
baserow:
106
+
assistantLLMModel: "groq/openai/gpt-oss-120b"
107
+
108
+
backendSecrets:
109
+
GROQ_API_KEY: "your-groq-api-key"
110
+
```
111
+
112
+
More information about the available providers can be found here: https://baserow.io/docs/installation%2Fai-assistant
113
+
114
+
### Enable Embeddings Service
115
+
116
+
The AI assistant uses the embeddings service and requires the LLM model to be configured. You need to enable this next to the global ai configuration.
117
+
118
+
#### Basic Configuration
119
+
120
+
```yaml
121
+
baserow-embeddings:
122
+
enabled: true
123
+
```
124
+
95
125
## Different Cloud Providers
96
126
97
127
On different cloud providers, you may need to configure the Object storage, ingress and Load Balancer differently. Below are some examples of how to configure them.
@@ -425,6 +455,29 @@ caddy:
425
455
| `baserow-celery-flower.args` | Arguments passed to the Celery Flower monitoring tool. | `["celery-flower"]` |
426
456
| `baserow-celery-flower.replicaCount` | Number of replicas for the Celery Flower monitoring tool. | `1` |
|`DISABLE_VOLUME_CHECK=true`|*Must be set to true*. Needed to disable the check designed to help non-technical users who are not configuring an external Postgres and S3. Because we are configuring external services we do not need any volume mounted into the container. |
214
214
|`BASEROW_PUBLIC_URL`| The public URL or IP that will be used to access baserow in your user's browser. Always should start with http:// https:// even if accessing via an IP address. |
215
215
|`DATABASE_HOST`| The hostname of the Postgres database Baserow will use to store its data in. |
@@ -371,7 +371,7 @@ in-tool settings, active enterprise licenses, promote other users to being staff
371
371
The `baserow/backend:1.35.3` and `baserow/web-frontend:1.35.3` images allow you to run
372
372
Baserow's various services as separate containers.
373
373
374
-
These images are used by the community Helm chart, our various docker-compose.yml
374
+
These images are used by the Official Helm chart, our various docker-compose.yml
375
375
example setups and are best for production environments where you want full control and
376
376
flexibility managing Baserow.
377
377
@@ -456,7 +456,7 @@ This service is our HTTP REST API service. When creating the task definition you
|`BASEROW_PUBLIC_URL`| The public URL or IP that will be used to access baserow in your user's browser. Always should start with http:// https:// even if accessing via an IP address. |
461
461
|`DATABASE_HOST`| The hostname of the Postgres database Baserow will use to store its data in. |
462
462
|`DATABASE_USER`| The username of the database user Baserow will use to connect to the database at `DATABASE_HOST`. |
0 commit comments