Skip to content

Commit 9c2a837

Browse files
committed
helm charts precisions
1 parent f0a7345 commit 9c2a837

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

docs/advanced/1_self_host/index.mdx

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -368,18 +368,20 @@ Detailed instructions in the official [repository][helm].
368368
### Enterprise deployment with Helm
369369

370370
The [Enterprise edition](../../misc/7_plans_details/index.mdx) of Windmill uses different base images and supports
371-
additional features. One important feature is better caching for dependencies in a
372-
super cache supported by S3.
371+
additional features.
373372

374-
You need:
373+
See the [Helm Chart repository README][helm] for more details.
375374

376-
- an Enterprise license key
377-
- an AWS account and S3 bucket
378-
- AWS credentials or IAM roles prepared for access from the Windmill worker pods.
379-
<br />
375+
To unlock EE, set in your values.yaml:
380376

381-
See the [Helm Chart repository README][helm] for more details. The exact setup
382-
for S3 access will vary according to your environment.
377+
```
378+
enterprise:
379+
enable: true
380+
```
381+
382+
You will want to disable the postgresql provided with the helm chart and set the database_url to your own managed postgresql.
383+
384+
For high-scale deployments (> 20 workers), we recommend using the [global S3 cache](../../misc/13_s3_cache/index.md). You will need an object storage compatible with the s3 protocol.
383385

384386
## Run Windmill without using a Postgres superuser
385387

0 commit comments

Comments
 (0)