mirror of
https://github.com/zitadel/zitadel.git
synced 2025-12-08 21:42:15 +00:00
docs: split out self-hosting into new section (#4903)
* docs: split out self-hosting into section * check for broken links * fix netlify proxy forward * use full path
This commit is contained in:
@@ -91,16 +91,16 @@ By default ZITADEL uses `RSA256` for signing purposes and `AES256` for encryptio
|
||||
### Masterkey
|
||||
|
||||
Since the Masterkey is used as means of protecting the Secrets Storage it cannot be stored in the storage.
|
||||
You find [here the many ways how ZITADEL can consume the Masterkey](../../guides/manage/self-hosted/configure).
|
||||
You find [here the many ways how ZITADEL can consume the Masterkey](/docs/self-hosting/manage/configure).
|
||||
|
||||
### TLS Material
|
||||
|
||||
ZITADEL does support end to end TLS as such it can consume TLS Key Material.
|
||||
Please check our [TLS Modes documentation](../../guides/manage/self-hosted/tls_modes) for more details.
|
||||
Please check our [TLS Modes documentation](/docs/self-hosting/manage/tls_modes) for more details.
|
||||
|
||||
### Admin User
|
||||
|
||||
The initial Admin User of ZITADEL can be configured through [ZITADELs config options](../../guides/manage/self-hosted/configure).
|
||||
The initial Admin User of ZITADEL can be configured through [ZITADELs config options](/docs/self-hosting/manage/configure).
|
||||
|
||||
:::info
|
||||
To prevent elevated breaches ZITADEL forces the Admin Users password to be changed during the first login.
|
||||
|
||||
@@ -72,7 +72,7 @@ The common update involves the following steps and do not need manual interventi
|
||||
- As soon as the new version is ready to accept traffic it will signal this on the readiness endpoint `/debug/ready`
|
||||
- At this point your network infrastructure can send traffic to the new version
|
||||
|
||||
Users who use [Kubernetes/Helm](../../guides/deploy/kubernetes) or serverless container services like Google Cloud Run can benefit from the fact the above process is automated.
|
||||
Users who use [Kubernetes/Helm](/docs/self-hosting/deploy/kubernetes) or serverless container services like Google Cloud Run can benefit from the fact the above process is automated.
|
||||
|
||||
:::info
|
||||
As a good practice we recommend creating Database Backups prior to an update.
|
||||
|
||||
Reference in New Issue
Block a user