andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-10-20 14:34:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: rename configuration to settings (#11568)

Browse Source 
# Which Problems Are Solved

naming inconsistencies: Configuration <-> Settings

# How the Problems Are Solved


# Additional Changes


# Additional Context

- Closes #11282
This commit is contained in:
Wim Van Laer
2026-02-18 14:25:42 +01:00
committed by GitHub
parent 64065bbe3c
commit 699ed17918
129 changed files with 359 additions and 359 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/examples/secure-api/python-django.mdx
+3 -3
View File
@@ -19,7 +19,7 @@ This documentation references our [example](https://github.com/zitadel/example-d
## ZITADEL setup
Before we can start building our application, we have to do a few configuration steps in ZITADEL Management Console.
Before we can start building our application, we have to do a few setup steps in ZITADEL Management Console.
### Create application
@@ -55,7 +55,7 @@ And the following from the Service Account:
For this example we need the following dependencies:
- `django`: to create an API with django
- `python-dotenv`: to use environment variables in the configuration
- `python-dotenv`: to use environment variables in the settings
- `authlib`: client-side OAuth functionality
- `requests`: HTTP requests for the introspection
@@ -85,7 +85,7 @@ There is info needed for the introspection calls, which we put into the settings
https://github.com/zitadel/example-python-django-oauth/blob/main/myapi/settings.py#L125-L133
```
and create a ".env"-file in the root folder with the configuration as an example:
and create a ".env"-file in the root folder with the settings as an example:
```bash
ZITADEL_INTROSPECTION_URL = 'URL to the introspection endpoint to verify the provided token'
ZITADEL_DOMAIN = 'Domain used as audience in the token verification'