chore: rename configuration to settings (#11568)

# 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
@@ -18,7 +18,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.
### Project roles
@@ -83,7 +83,7 @@ The secret will not be displayed again, but you can regenerate one if you loose
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
- `mozilla-django-oidc`: client-side OIDC functionality
For the dependencies we need a requirements.txt-file with the following content:
@@ -137,13 +137,13 @@ AUTHENTICATION_BACKENDS = (
)
```
Add configuration:
Add settings:
```python reference
https://github.com/zitadel/example-python-django-oidc/blob/main/mysite/settings.py#L130-L174
```
and create a ".env"-file in the root folder with the configuration:
and create a ".env"-file in the root folder with the settings:
```bash
ZITADEL_PROJECT = "ID of the project you created the application in ZITADEL"