From 6600163137075761a0820f721827f573caeb500b Mon Sep 17 00:00:00 2001 From: Vladi Bilonenko Date: Thu, 17 Nov 2022 08:00:32 +0100 Subject: [PATCH 1/2] Release v0.10 documentation --- content/docs/configuration/environment-variables.md | 10 ++++++++++ content/docs/self-hosting/docker.md | 7 ++++--- content/docs/self-hosting/upgrade.md | 6 ++++-- 3 files changed, 18 insertions(+), 5 deletions(-) diff --git a/content/docs/configuration/environment-variables.md b/content/docs/configuration/environment-variables.md index 06d7895d..8a84c11b 100644 --- a/content/docs/configuration/environment-variables.md +++ b/content/docs/configuration/environment-variables.md @@ -42,6 +42,7 @@ Optionally, secure deployment with Google IAP. You have 2 options: | `DEKART_DATASOURCE=BQ`
version >= 0.8 | Which datasource to use:
Values| | `DEKART_STORAGE=GCS`
version >= 0.8 | Which storage backend to use for storing queries and query results
Values| | `DEKART_CLOUD_STORAGE_BUCKET` | Google Cloud Storage or AWS S3 bucket name where Dekart Query results will be stored.
*Example*: `dekart-bucket`| +| `DEKART_CORS_ORIGIN=`
version >= 0.10 | 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.
*Example*: `https://dekart.example.com` | ## AWS @@ -77,6 +78,15 @@ Required to query BigQuery and use Cloud Storage | `DEKART_BIGQUERY_MAX_BYTES_BILLED`
version >= 0.7 | Sets `maximumBytesBilled` in BigQuery Job Configuration to implement Best Practices for Controlling Query Cost.
If not set warning message will appear in logs.| +## File upload + +Starting from version 0.10 Dekart supports file upload. File upload is disabled by default. Once uploaded file are stored in a same storage as query results. Both AWS S3 and Google Cloud Storage are supported. Recommended max file size is 100MB. + +| Name | Description | +| ------------- | ------------- | +| `DEKART_ALLOW_FILE_UPLOAD`
version >= 0.10 | Enable file upload
*Example value*: `1`| + + ## User authorization via Google IAP Dekart can read claims provided by Google IAP and authorize users to: diff --git a/content/docs/self-hosting/docker.md b/content/docs/self-hosting/docker.md index 7c2d3a90..cfdfd338 100644 --- a/content/docs/self-hosting/docker.md +++ b/content/docs/self-hosting/docker.md @@ -41,9 +41,9 @@ docker run \ -e DEKART_ATHENA_CATALOG=${DEKART_ATHENA_CATALOG} \ -e DEKART_ATHENA_S3_OUTPUT_LOCATION=${DEKART_ATHENA_S3_OUTPUT_LOCATION} \ -e DEKART_MAPBOX_TOKEN=${DEKART_MAPBOX_TOKEN} \ - -e DEKART_MAPBOX_TOKEN=${DEKART_MAPBOX_TOKEN} \ + -e DEKART_CORS_ORIGIN=${DEKART_CORS_ORIGIN} \ -p 8080:8080 \ - dekartxyz/dekart:0.9 + dekartxyz/dekart:0.10 ``` @@ -73,8 +73,9 @@ docker run \ -e DEKART_BIGQUERY_PROJECT_ID=${DEKART_BIGQUERY_PROJECT_ID} \ -e DEKART_BIGQUERY_MAX_BYTES_BILLED=53687091200 \ -e DEKART_MAPBOX_TOKEN=${DEKART_MAPBOX_TOKEN} \ + -e DEKART_CORS_ORIGIN=${DEKART_CORS_ORIGIN} \ -p 8080:8080 \ - dekartxyz/dekart:0.9 + dekartxyz/dekart:0.10 ``` See details on [environment variables](/docs/configuration/environment-variables) diff --git a/content/docs/self-hosting/upgrade.md b/content/docs/self-hosting/upgrade.md index 3f97bb81..a26249f6 100644 --- a/content/docs/self-hosting/upgrade.md +++ b/content/docs/self-hosting/upgrade.md @@ -18,10 +18,12 @@ Before you begin: it is always recommended to backup your postgres database befo For all Docker based deployments, update docker tag, for example: -`dekartxyz/dekart:0.8` -> `dekartxyz/dekart:0.9` +`dekartxyz/dekart:0.9` -> `dekartxyz/dekart:0.10` + +Configure `DEKART_CORS_ORIGIN` environment variable to ensure security of your instance and prevent warnings in logs. Then redeploy application ## Migration instructions -There is no breaking configuration changes in version `0.9` \ No newline at end of file +There is no breaking configuration changes in version `0.10` \ No newline at end of file From 7c672480c9120003df6da6a6b86826742feb9d66 Mon Sep 17 00:00:00 2001 From: Vladi Bilonenko Date: Fri, 18 Nov 2022 07:49:43 +0100 Subject: [PATCH 2/2] Fix deployment from feature branches --- .github/workflows/pages.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.github/workflows/pages.yaml b/.github/workflows/pages.yaml index f960a7b6..df588492 100644 --- a/.github/workflows/pages.yaml +++ b/.github/workflows/pages.yaml @@ -1,5 +1,9 @@ name: Publish Pages -on: [push] +on: + pull_request: + push: + branches: + - main jobs: publish: runs-on: ubuntu-latest @@ -15,6 +19,7 @@ jobs: - run: npm run build - name: Deploy + if: github.event_name != 'pull_request' uses: JamesIves/github-pages-deploy-action@4.0.0 with: branch: gh-pages