website/docs: remove references to legacy Docker Compose v1 (#8138)
This commit is contained in:
@ -17,7 +17,7 @@ If you omit the `-S` parameter, the email will be sent using the global settings
|
||||
To run this command with docker-compose, use
|
||||
|
||||
```
|
||||
docker-compose exec worker ak test_email [...]
|
||||
docker compose exec worker ak test_email [...]
|
||||
```
|
||||
|
||||
To run this command with Kubernetes, use
|
||||
|
@ -29,7 +29,7 @@ Add the following block to your `.env` file:
|
||||
AUTHENTIK_LOG_LEVEL=trace
|
||||
```
|
||||
|
||||
Afterwards, run `docker-compose up -d`.
|
||||
Afterwards, run `docker compose up -d`.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="kubernetes">
|
||||
|
@ -5,7 +5,7 @@ title: Troubleshooting LDAP Synchronization
|
||||
To troubleshoot LDAP sources, you can run the command below to run a synchronization in the foreground and see any errors or warnings that might happen directly
|
||||
|
||||
```
|
||||
docker-compose run --rm worker ldap_sync *slug of the source*
|
||||
docker compose run --rm worker ldap_sync *slug of the source*
|
||||
```
|
||||
|
||||
or, for Kubernetes, run
|
||||
@ -17,7 +17,7 @@ kubectl exec -it deployment/authentik-worker -c authentik -- ak ldap_sync *slug
|
||||
Starting with authentik 2023.10, you can also run command below to explicitly check the connectivity to the configured LDAP Servers:
|
||||
|
||||
```
|
||||
docker-compose run --rm worker ldap_check_connection *slug of the source*
|
||||
docker compose run --rm worker ldap_check_connection *slug of the source*
|
||||
```
|
||||
|
||||
or, for Kubernetes, run
|
||||
|
@ -11,7 +11,7 @@ This recovery key will give whoever has the link direct access to your instances
|
||||
To create the key, run the following command:
|
||||
|
||||
```
|
||||
docker-compose run --rm server create_recovery_key 10 akadmin
|
||||
docker compose run --rm server create_recovery_key 10 akadmin
|
||||
```
|
||||
|
||||
For Kubernetes, run
|
||||
|
@ -7,7 +7,7 @@ If all of the Admin groups have been deleted, or misconfigured during sync, you
|
||||
Run the following command, where _username_ is the user you want to add to the newly created group:
|
||||
|
||||
```
|
||||
docker-compose run --rm server create_admin_group username
|
||||
docker compose run --rm server create_admin_group username
|
||||
```
|
||||
|
||||
or, for Kubernetes, run
|
||||
|
@ -9,7 +9,7 @@ The error should be temporary and not occur after initial installation.
|
||||
If it does, you can run the following command to ensure all permissions exist:
|
||||
|
||||
```
|
||||
docker-compose run --rm worker repair_permissions
|
||||
docker compose run --rm worker repair_permissions
|
||||
```
|
||||
|
||||
or, for Kubernetes, run
|
||||
|
Reference in New Issue
Block a user