centersl/n8n-docs
1
0
Fork 0
mirror of https://github.com/n8n-io/n8n-docs.git synced 2026-03-27 09:28:43 +07:00
Code Issues Packages Projects Releases Wiki Activity

Update existing /hosting/scaling/ link s to /hosting/scaling/overview

Browse Source
This commit is contained in:
freakwriter
2024-07-01 13:25:11 -04:00
parent 2c22bcf169
commit 08be0e9dbb
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
_snippets/self-hosting/installation/server-setups-next-steps.md
View File

@@ -1,2 +1,2 @@
* Learn more about [configuring](/hosting/configuration/environment-variables/) and [scaling](/hosting/scaling/) n8n.
* Learn more about [configuring](/hosting/configuration/environment-variables/) and [scaling](/hosting/scaling/overview) n8n.
* Or explore using n8n: try the [Quickstarts](/try-it-out/).

4
docs/1-0-migration-checklist.md
View File

@@ -43,7 +43,7 @@ n8n has removed support for MySQL and MariaDB as storage backends for n8n. These
Previously, you could use the `EXECUTIONS_PROCESS` environment variable to specify whether executions should run in the `main` process or in their `own` processes. This option and `own` mode are now deprecated and will be removed in a future version of n8n. This is because it led to increased code complexity while offering marginal benefits. Starting from n8n 1.0, `main` will be the new default.
Note that executions start much faster in `main` mode than in `own` mode. However, if a workflow consumes more memory than is available, it might crash the entire n8n application instead of just the worker thread. To mitigate this, make sure to allocate enough system resources or configure [queue mode](https://docs.n8n.io/hosting/scaling/queue-mode/) to distribute executions among multiple workers.
Note that executions start much faster in `main` mode than in `own` mode. However, if a workflow consumes more memory than is available, it might crash the entire n8n application instead of just the worker thread. To mitigate this, make sure to allocate enough system resources or configure [queue mode](/hosting/scaling/queue-mode/) to distribute executions among multiple workers.
[PR #6196](https://github.com/n8n-io/n8n/pull/6196){:target=_blank .external link}
@@ -122,7 +122,7 @@ If you build custom nodes, refer to [HTTP request helpers](/integrations/creatin
### Removed WEBHOOK_TUNNEL_URL
As of version 0.227.0, n8n has renamed the `WEBHOOK_TUNNEL_URL` configuration option to `WEBHOOK_URL`. In n8n 1.0, `WEBHOOK_TUNNEL_URL` has been removed. Update your setup to reflect the new name. For more information about this configuration option, refer to [the docs](/hosting/configuration/configuration-methods/#webhook-url).
As of version 0.227.0, n8n has renamed the `WEBHOOK_TUNNEL_URL` configuration option to `WEBHOOK_URL`. In n8n 1.0, `WEBHOOK_TUNNEL_URL` has been removed. Update your setup to reflect the new name. For more information about this configuration option, refer to [the docs](/hosting/configuration/configuration-examples/webhook-url/).
[PR #1408](https://github.com/n8n-io/n8n/pull/1408){:target=_blank .external link}

2
docs/hosting/installation/server-setups/aws.md
View File

@@ -80,7 +80,7 @@ The `postgres-deployment.yaml` manifest then uses the values from this manifest
### Create a volume for file storage
While not essential for running n8n, using persistent volumes helps maintain files uploaded while using n8n and if you want to persist [manual n8n encryption keys](https://docs.n8n.io/hosting/configuration/#encryption-key) between restarts, which saves a file containing the key into file storage during startup.
While not essential for running n8n, using persistent volumes helps maintain files uploaded while using n8n and if you want to persist [manual n8n encryption keys](/hosting/configuration/environment-variables/) between restarts, which saves a file containing the key into file storage during startup.
The `n8n-claim0-persistentvolumeclaim.yaml` manifest creates this, and the n8n Deployment mounts that claim in the `volumes` section of the `n8n-deployment.yaml` manifest.