a few more fixes

This commit is contained in:
Deborah Barnard
2024-01-25 10:52:07 +00:00
parent b993487f03
commit ef7351319d
4 changed files with 5 additions and 5 deletions

View File

@@ -1,5 +1,5 @@
StylesPath = "styles"
MinAlertLevel = warning
MinAlertLevel = error
Vocab = default
[*.md]
BasedOnStyles = from-alex, from-write-good, n8n-styles, from-microsoft, Vale

View File

@@ -39,7 +39,7 @@ If the API you're using allows you to target a particular page by number:
1. Hover over **Value** and toggle **Expression** on.
1. Enter `{{ $pageCount + 1 }}`
`$pageCount` is the number of pages the HTTP Request node has fetched. It starts at zero. Most API pagination counts from one (the first page is page one). So adding `+1` to `$pageCount` means the node fetches page one on its first loop, page two on its second, and so on.
`$pageCount` is the number of pages the HTTP Request node has fetched. It starts at zero. Most API pagination counts from one (the first page is page one). This means that adding `+1` to `$pageCount` means the node fetches page one on its first loop, page two on its second, and so on.
## Set the page size in the query

View File

@@ -133,11 +133,11 @@ export VUE_APP_URL_BASE_API=https://n8n.example.com/
n8n creates a random encryption key automatically on the first launch and saves
it in the `~/.n8n` folder. n8n uses that key to encrypt the credentials before
they get saved to the database. If the key is not yet in the settings file,
they get saved to the database. If the key isn't yet in the settings file,
you can set it using an environment variable, so that n8n
uses your custom key instead of generating a new one.
In queue mode, it is required to specify the encryption key environment variable for all workers.
In queue mode, you must specify the encryption key environment variable for all workers.
```bash
export N8N_ENCRYPTION_KEY=<SOME RANDOM STRING>

View File

@@ -63,7 +63,7 @@ For larger scale n8n deployments, Postgres provides a more robust database backe
### Create a volume for persistent storage
To maintain data between pod restarts, the Postgres deployment needs a persistent volume. Running Postgres on GCP requires a specific Kubernetes Storage Class. You can read [this guide](https://cloud.google.com/architecture/deploying-highly-available-postgresql-with-gke){:target="_blank" .external-link} for specifics, but the `storage.yaml` manifest creates it for you. You may want to change the regions to create the storage in under the `allowedTopologies` > `matchedLabelExpressions` > `values` key. By default, they're set to "us-central".
To maintain data between pod restarts, the Postgres deployment needs a persistent volume. Running Postgres on GCP requires a specific Kubernetes Storage Class. You can read [this guide](https://cloud.google.com/architecture/deploying-highly-available-postgresql-with-gke){:target="_blank" .external-link} for specifics, but the `storage.yaml` manifest creates it for you. You may want to change the regions to create the storage in under the `allowedTopologies` > `matchedLabelExpressions` > `values` key. By default, they're set to `us-central`.
```yaml