You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/topics/MultiTenancy.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,14 +17,14 @@ Multi-tenancy works by extracting a tenant name from the request URL and passing
17
17
18
18
The simplest approach is to extract the tenant name in a rewrite rule and set a corresponding header which will be read by the QWC services. This can be accomplished as follows:
19
19
20
-
1. Define the name of the tenant header in `qwc-docker/docker-compose.yml` by setting the `TENANT_HEADER` environment variable in the `qwc-service-variables` block, i.e.:
20
+
- Define the name of the tenant header in `qwc-docker/docker-compose.yml` by setting the `TENANT_HEADER` environment variable in the `qwc-service-variables` block, i.e.:
21
21
```yml
22
22
x-qwc-service-variables: &qwc-service-variables
23
23
[...]
24
24
TENANT_HEADER: Tenant
25
25
```
26
26
27
-
2. Add rewrite rules to the `api-gateway` configuration file `qwc-docker/api-gateway/nginx.conf`, extracting the tenant name and setting the tenant header. For example
27
+
- Add rewrite rules to the `api-gateway` configuration file `qwc-docker/api-gateway/nginx.conf`, extracting the tenant name and setting the tenant header. For example
0 commit comments