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: content/docs/configuration/environment-variables.md
+12-1Lines changed: 12 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ images: []
22
22
|`DEKART_POSTGRES_PASSWORD`|*Example*: `******`|
23
23
|`DEKART_PORT`|*Example*: `8080`|
24
24
|`DEKART_POSTGRES_URL` <br><smallclass="badge badge-info">version >= 0.13</small> | Alternatively to specify `DEKART_POSTGRES_DB`, `DEKART_POSTGRES_HOST`, `DEKART_POSTGRES_PORT`, `DEKART_POSTGRES_USER`, `DEKART_POSTGRES_PASSWORD`, configure PostgreSQL by passing the connection string. If both specified `DEKART_POSTGRES_URL` is used. <br/> *Example*: `postgres://user:pass@hostname:5432/dekart?sslmode=verify-full`|
25
-
|`DEKART_DATASOURCE=BQ` <br><smallclass="badge badge-info">version >= 0.8</small> | Which datasource to use: <br>Values<ul><li>`BQ` BigQuery, default</li><li>`ATHENA` AWS Athena</li><li>`SNOWFLAKE` Snowflake <smallclass="badge badge-info">version >= 0.12</small></li></ul>|
|`DEKART_STORAGE=GCS` <br><smallclass="badge badge-info">version >= 0.8</small> | Which storage backend to use for storing queries and query results <br>Values<ul><li>`GCS` Google Cloud Storage, default, works only with BigQuery data source</li><li>`S3` AWS S3, works with BigQuery and AWS Athena</li></ul>|
27
27
|`DEKART_CLOUD_STORAGE_BUCKET`| Google Cloud Storage or AWS S3 bucket name where Dekart Query results will be stored. <br> *Example*: `dekart-bucket` <br><br> If value is empty, users will be able to define storage bucket via UI. Supported datasource `DEKART_DATASOURCE`: <ul><li>`BQ` BigQuery from <smallclass="badge badge-info">version >= 0.15</small></li></ul>|
28
28
|`DEKART_CORS_ORIGIN=` <br/><smallclass="badge badge-info">version >= 0.10</small> | CORS Origin to be allowed by Dekart backend and set in `Access-Control-Allow-Origin` header. If not set or set incorrectly, warning will appear in logs. If set incorrectly. <br> *Example*: `https://dekart.example.com`|
@@ -71,6 +71,14 @@ Required to query BigQuery and use Cloud Storage
71
71
|`DEKART_SNOWFLAKE_USER` <br/><smallclass="badge badge-info">version >= 0.12</small> | Snowflake user with default warehouse configured <br> *Example*: `example_user`|
Postgres can be used as a data source for Dekart. Do not confuse with Dekart's Postgres database, which is used to store query meta information.
77
+
78
+
| Name | Description |
79
+
| ------------- | ------------- |
80
+
|`DEKART_POSTGRES_DATA_CONNECTION` <br/><smallclass="badge badge-info">version >= 0.16</small> | Postgres DB to be used as data source <br> *Example*: `postgres://user:password@host:port/db`|
81
+
74
82
75
83
## File upload
76
84
@@ -143,6 +151,9 @@ Dekart can read <a target="_blank" href="https://docs.aws.amazon.com/elasticload
143
151
|`DEKART_UX_DATA_DOCUMENTATION`| Allows provide URL to dataset documentation. It will appear in Dekart UI.<br> *Example value*: `https://my.company/dataset/schema.html`|
144
152
|`DEKART_HTML_CUSTOM_CODE`| Allows to add custom HTML code to `<head>`. Can be used for adding trackers. |
145
153
|`DEKART_DISABLE_USAGE_STATS` <br><smallclass="badge badge-info">version >= 0.11</small> | By default, Dekart appends certain information to the referrer of external links. This information includes the version number, the SHA256 hash of the hostname, the name of the data source, and the total number of reports, queries, files, and authors. No other information is collected. The source code for this implementation can be found [here](https://github.com/dekart-xyz/dekart/blob/main/src/client/lib/ref.js#L25). This behavior can be turned off by setting this variable to `1`.|
154
+
|`DEKART_UX_ACCESS_ERROR_INFO_HTML` <br><smallclass="badge badge-info">version >= 0.16</small> | Allows to provide custom HTML code to be shown on the access error page. |
155
+
|`DEKART_UX_NOT_FOUND_ERROR_INFO_HTML` <br><smallclass="badge badge-info">version >= 0.16</small> | Allows to provide custom HTML code to be shown on the not found error page. |
156
+
|`DEKART_UX_SAMPLE_QUERY_SQL` <br><smallclass="badge badge-info">version >= 0.16</small> | Allows to provide a sample SQL query to be shown in the query editor. |
Copy file name to clipboardExpand all lines: content/docs/self-hosting/upgrade.md
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -16,10 +16,13 @@ menu:
16
16
Before you begin: it is always recommended to back up your Postgres database before upgrading Dekart. On the first run, Dekart applies migrations to the database and you won't be able to downgrade.
17
17
</div></p>
18
18
19
-
For all Docker-based deployments, update the docker tag, for example `dekartxyz/`dekart:0.14` -> `dekartxyz/dekart:0.15`
19
+
For all Docker-based deployments, update the docker tag, for example `dekartxyz/`dekart:0.15` -> `dekartxyz/dekart:0.16`
0 commit comments