diff --git a/apps/docs/content/apis/benchmarks/index.mdx b/apps/docs/content/apis/benchmarks/index.mdx index 7b693f033..b6f867a41 100644 --- a/apps/docs/content/apis/benchmarks/index.mdx +++ b/apps/docs/content/apis/benchmarks/index.mdx @@ -22,7 +22,7 @@ The primary goal is to assess if ZITADEL can scale to required proportion. The g ## Procedure -First we determine the “target” of our load-test. The target is expressed as a make recipe in the load-test [Makefile](https://github.com/zitadel/zitadel/blob/main/load-test/Makefile). See also the load-test [readme](https://github.com/zitadel/zitadel/blob/main/load-test/README.md) on how to configure and run load-tests. +First we determine the “target” of our load-test. The target is expressed as a make recipe in the benchmark [Makefile](https://github.com/zitadel/zitadel/blob/main/benchmark/Makefile). See also the benchmark [readme](https://github.com/zitadel/zitadel/blob/main/benchmark/README.md) on how to configure and run load-tests. A target should be tested for longer periods of time, as it might take time for certain metrics to show up. For example, cloud SQL samples query insights. A runtime of at least **30 minutes** is advised at the moment. After each iteration of load-test, we should consult the [After test procedure](#after-test-procedure) to conclude an outcome: @@ -35,7 +35,7 @@ After each iteration of load-test, we should consult the [After test procedure]( ### Benchmark definition -Tests are implemented in the ecosystem of [k6](https://k6.io). The tests are publicly available in the [zitadel repository](https://github.com/zitadel/zitadel/tree/main/load-test). Custom extensions of k6 are implemented in the [xk6-modules repository](https://github.com/zitadel/xk6-modules). +Tests are implemented in the ecosystem of [k6](https://k6.io). The tests are publicly available in the [zitadel repository](https://github.com/zitadel/zitadel/tree/main/benchmark). Custom extensions of k6 are implemented in the [xk6-modules repository](https://github.com/zitadel/xk6-modules). The tests must at least measure the request duration for each API call. This gives an indication on how zitadel behaves over the duration of the load test. ### Metrics @@ -73,7 +73,7 @@ The following metrics must be collected for each test iteration. The metrics are #### Make recipes -Details about the tests implemented can be found in [this readme](https://github.com/zitadel/zitadel/blob/main/load-test/README.md#test). +Details about the tests implemented can be found in [this readme](https://github.com/zitadel/zitadel/blob/main/benchmark/README.md#test). ### Test conclusion diff --git a/apps/docs/content/guides/integrate/login-ui/login-app.mdx b/apps/docs/content/guides/integrate/login-ui/login-app.mdx index 9013f9152..ecdc3fcce 100644 --- a/apps/docs/content/guides/integrate/login-ui/login-app.mdx +++ b/apps/docs/content/guides/integrate/login-ui/login-app.mdx @@ -130,7 +130,7 @@ When setting up the new Login app for OIDC, ensure it meets the following requir - The OIDC Proxy sets `x-zitadel-public-host` which is the host, your Login app is deployed to `ex. login.example.com`. - The OIDC Proxy sets `x-zitadel-instance-host` which is the host of your instance `ex. test-hdujwl.zitadel.cloud`. -You can review an example implementation of a middleware [here](https://github.com/zitadel/zitadel/blob/main/apps/login/src/middleware.ts). +You can review an example implementation of a middleware [here](https://github.com/zitadel/zitadel/blob/main/apps/login/src/proxy.ts). #### Deploy to Vercel diff --git a/apps/docs/content/index.mdx b/apps/docs/content/index.mdx index c38b0a2bc..7e2b665a0 100644 --- a/apps/docs/content/index.mdx +++ b/apps/docs/content/index.mdx @@ -126,7 +126,7 @@ Join the community and get help. /> } description="Help us improve ZITADEL and its documentation." />