mirror of
https://github.com/awatertrevi/infisical.git
synced 2026-10-08 10:28:00 +00:00
Merge pull request #2366 from ThallesP/patch-1
docs: add mention of SITE_URL as being required
This commit is contained in:
@@ -20,7 +20,7 @@ Used to configure platform-specific security and operational settings
|
|||||||
-base64 32`
|
-base64 32`
|
||||||
</ParamField>
|
</ParamField>
|
||||||
|
|
||||||
<ParamField query="SITE_URL" type="string" default="none" optional>
|
<ParamField query="SITE_URL" type="string" default="none" required>
|
||||||
Must be an absolute URL including the protocol (e.g.
|
Must be an absolute URL including the protocol (e.g.
|
||||||
https://app.infisical.com).
|
https://app.infisical.com).
|
||||||
</ParamField>
|
</ParamField>
|
||||||
|
|||||||
@@ -41,7 +41,7 @@ description: "Learn how to use Helm chart to install Infisical on your Kubernete
|
|||||||
|
|
||||||
To deploy this Helm chart, a Kubernetes secret named `infisical-secrets` must be present in the same namespace where the chart is being deployed.
|
To deploy this Helm chart, a Kubernetes secret named `infisical-secrets` must be present in the same namespace where the chart is being deployed.
|
||||||
|
|
||||||
For a minimal installation of Infisical, you need to configure `ENCRYPTION_KEY`, `AUTH_SECRET`, `DB_CONNECTION_URI`, and `REDIS_URL`. [Learn more about configuration settings](/self-hosting/configuration/envars).
|
For a minimal installation of Infisical, you need to configure `ENCRYPTION_KEY`, `AUTH_SECRET`, `DB_CONNECTION_URI`, `SITE_URL`, and `REDIS_URL`. [Learn more about configuration settings](/self-hosting/configuration/envars).
|
||||||
|
|
||||||
|
|
||||||
<Tabs>
|
<Tabs>
|
||||||
@@ -56,6 +56,7 @@ description: "Learn how to use Helm chart to install Infisical on your Kubernete
|
|||||||
stringData:
|
stringData:
|
||||||
AUTH_SECRET: <>
|
AUTH_SECRET: <>
|
||||||
ENCRYPTION_KEY: <>
|
ENCRYPTION_KEY: <>
|
||||||
|
SITE_URL: <>
|
||||||
```
|
```
|
||||||
</Tab>
|
</Tab>
|
||||||
<Tab title="Production deployment">
|
<Tab title="Production deployment">
|
||||||
@@ -71,6 +72,7 @@ description: "Learn how to use Helm chart to install Infisical on your Kubernete
|
|||||||
ENCRYPTION_KEY: <>
|
ENCRYPTION_KEY: <>
|
||||||
REDIS_URL: <>
|
REDIS_URL: <>
|
||||||
DB_CONNECTION_URI: <>
|
DB_CONNECTION_URI: <>
|
||||||
|
SITE_URL: <>
|
||||||
```
|
```
|
||||||
</Tab>
|
</Tab>
|
||||||
</Tabs>
|
</Tabs>
|
||||||
|
|||||||
@@ -28,7 +28,7 @@ The following guide provides a detailed step-by-step walkthrough on how you can
|
|||||||
|
|
||||||
</Step>
|
</Step>
|
||||||
<Step title="Start Infisical">
|
<Step title="Start Infisical">
|
||||||
For a minimal installation of Infisical, you must configure `ENCRYPTION_KEY`, `AUTH_SECRET`, `DB_CONNECTION_URI`, and `REDIS_URL`. [View all available configurations](/self-hosting/configuration/envars).
|
For a minimal installation of Infisical, you must configure `ENCRYPTION_KEY`, `AUTH_SECRET`, `DB_CONNECTION_URI`, `SITE_URL`, and `REDIS_URL`. [View all available configurations](/self-hosting/configuration/envars).
|
||||||
|
|
||||||
|
|
||||||
We recommend using Cloud-based Platform as a Service (PaaS) solutions for PostgreSQL and Redis to ensure high availability.
|
We recommend using Cloud-based Platform as a Service (PaaS) solutions for PostgreSQL and Redis to ensure high availability.
|
||||||
@@ -43,6 +43,7 @@ The following guide provides a detailed step-by-step walkthrough on how you can
|
|||||||
-e AUTH_SECRET="q6LRi7c717a3DQ8JUxlWYkZpMhG4+RHLoFUVt3Bvo2U=" \
|
-e AUTH_SECRET="q6LRi7c717a3DQ8JUxlWYkZpMhG4+RHLoFUVt3Bvo2U=" \
|
||||||
-e DB_CONNECTION_URI="<>" \
|
-e DB_CONNECTION_URI="<>" \
|
||||||
-e REDIS_URL="<>" \
|
-e REDIS_URL="<>" \
|
||||||
|
-e SITE_URL="<>" \
|
||||||
infisical/infisical:<version>
|
infisical/infisical:<version>
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user