From 2c36927c1026f9fc5900239699d2bd409a951b35 Mon Sep 17 00:00:00 2001 From: Naveen MR Date: Sun, 5 Jun 2022 12:20:22 +0100 Subject: [PATCH] docs: env variables reorder --- .../content/en/getting-started/installation.md | 9 --------- .../noco-docs/content/en/getting-started/installation.md | 8 ++++---- 2 files changed, 4 insertions(+), 13 deletions(-) diff --git a/packages/noco-docs-prev/content/en/getting-started/installation.md b/packages/noco-docs-prev/content/en/getting-started/installation.md index db862d07ef..2c030240d1 100644 --- a/packages/noco-docs-prev/content/en/getting-started/installation.md +++ b/packages/noco-docs-prev/content/en/getting-started/installation.md @@ -147,15 +147,6 @@ If you plan to input some special characters, you may need to change the charact | NC_SENTRY_DSN | No | For Sentry monitoring | | | NC_DISABLE_ERR_REPORT | No | Disable error reporting | | -## Litestream : SQLite backup -If below environment variables are present - SQLite database (NC_DB) will be backed up to S3 - -| Variable | Mandatory | Comments | If absent | -|-------------------------|-----------|----------------------------------------------------------------------------------|--------------------------------------------| -| AWS_ACCESS_KEY_ID | No | For Litestream - S3 access key id | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | -| AWS_SECRET_ACCESS_KEY | No | For Litestream - S3 secret access key | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | -| AWS_BUCKET | No | For Litestream - S3 bucket | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | -| AWS_BUCKET_PATH | No | For Litestream - S3 bucket path (like folder within S3 bucket) | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | ### Docker Compose diff --git a/packages/noco-docs/content/en/getting-started/installation.md b/packages/noco-docs/content/en/getting-started/installation.md index 91f4ee3ff3..9214e07775 100644 --- a/packages/noco-docs/content/en/getting-started/installation.md +++ b/packages/noco-docs/content/en/getting-started/installation.md @@ -174,10 +174,6 @@ By default, SQLite is used for storing meta data. However, you can specify your | Variable | Mandatory | Comments | If absent | | |------------------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|---| -| AWS_ACCESS_KEY_ID | No | For Litestream - S3 access key id | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | | -| AWS_SECRET_ACCESS_KEY | No | For Litestream - S3 secret access key | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | | -| AWS_BUCKET | No | For Litestream - S3 bucket | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | | -| AWS_BUCKET_PATH | No | For Litestream - S3 bucket path (like folder within S3 bucket) | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | | | DB_QUERY_LIMIT_DEFAULT | No | Default pagination limit | 25 | | | DB_QUERY_LIMIT_MAX | No | Maximum allowed pagination limit | 100 | | | DB_QUERY_LIMIT_MIN | No | Minimum allowed pagination limit | 1 | | @@ -208,6 +204,10 @@ By default, SQLite is used for storing meta data. However, you can specify your | NC_REDIS_URL | No | Custom Redis URL. Example: `redis://:authpassword@127.0.0.1:6380/4` | Meta data will be stored in memory | | | NC_DISABLE_CACHE | No | To be used only while debugging. On setting this to `true` - meta data be fetched from db instead of redis/cache. | `false` | | | NC_BASEURL_INTERNAL | No | Used as base url for internal(server) API calls | Default value in docker will be `http://localhost:$PORT` and in all other case it's populated from request object | | +| AWS_ACCESS_KEY_ID | No | For Litestream - S3 access key id | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | | +| AWS_SECRET_ACCESS_KEY | No | For Litestream - S3 secret access key | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | | +| AWS_BUCKET | No | For Litestream - S3 bucket | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | | +| AWS_BUCKET_PATH | No | For Litestream - S3 bucket path (like folder within S3 bucket) | If Litestream is configured and NC_DB is not present. SQLite gets backed up to S3 | | ### AWS ECS (Fargate)