diff --git a/website/developer-docs/setup/frontend-dev-environment.md b/website/developer-docs/setup/frontend-dev-environment.md index 30a26765ec..e38b41ab38 100644 --- a/website/developer-docs/setup/frontend-dev-environment.md +++ b/website/developer-docs/setup/frontend-dev-environment.md @@ -45,7 +45,7 @@ Depending on platform, some native dependencies might be required. On macOS, run This makes the local web files and the config file available to the authentik server. -5. Run `docker-compose up -d` to apply those changes to your containers. +5. Run `docker compose up -d` to apply those changes to your containers. 6. `cd web` 7. Run `npm i` and then `npm run watch` to start the build process. diff --git a/website/docs/core/certificates.md b/website/docs/core/certificates.md index e41763626c..1e968df393 100644 --- a/website/docs/core/certificates.md +++ b/website/docs/core/certificates.md @@ -98,7 +98,7 @@ services: - --dns-route53 ``` -Afterwards, run `docker-compose up -d`, which will start certbot and generate your certificate. Within a few minutes, you'll see the certificate in your authentik interface. (If the certificate does not appear, restart the worker container. This is caused by incompatible permissions set by certbot). +Afterwards, run `docker compose up -d`, which will start certbot and generate your certificate. Within a few minutes, you'll see the certificate in your authentik interface. (If the certificate does not appear, restart the worker container. This is caused by incompatible permissions set by certbot). Navigate to _System -> Brands_, edit any brand and select the certificate of your choice. diff --git a/website/docs/flow/stages/email/index.mdx b/website/docs/flow/stages/email/index.mdx index a7751e2953..556b45878e 100644 --- a/website/docs/flow/stages/email/index.mdx +++ b/website/docs/flow/stages/email/index.mdx @@ -72,7 +72,7 @@ volumeMounts: :::info -If you've add the line and created a file, and can't see if, check the worker logs using `docker-compose logs -f worker` or `kubectl logs -f deployment/authentik-worker`. +If you've add the line and created a file, and can't see if, check the worker logs using `docker compose logs -f worker` or `kubectl logs -f deployment/authentik-worker`. ::: ![](custom_template.png) diff --git a/website/docs/installation/beta.mdx b/website/docs/installation/beta.mdx index 6f02522670..6a548934d7 100644 --- a/website/docs/installation/beta.mdx +++ b/website/docs/installation/beta.mdx @@ -64,8 +64,8 @@ Next, run the upgrade commands below. ```shell -docker-compose pull -docker-compose up -d +docker compose pull +docker compose up -d ``` diff --git a/website/docs/installation/configuration.mdx b/website/docs/installation/configuration.mdx index 13646e92a2..9bf19e8516 100644 --- a/website/docs/installation/configuration.mdx +++ b/website/docs/installation/configuration.mdx @@ -25,7 +25,7 @@ import TabItem from "@theme/TabItem"; If you are using Docker Compose, edit your .env file to append any keys that you want to add, and then run the following command to apply them: ``` - docker-compose up -d + docker compose up -d ``` @@ -49,7 +49,7 @@ To check if your config has been applied correctly, you can run the following co ``` - docker-compose run --rm worker dump_config + docker compose run --rm worker dump_config ``` diff --git a/website/docs/installation/docker-compose.md b/website/docs/installation/docker-compose.md index 372510d8e3..ac14e341a9 100644 --- a/website/docs/installation/docker-compose.md +++ b/website/docs/installation/docker-compose.md @@ -76,7 +76,7 @@ COMPOSE_PORT_HTTP=80 COMPOSE_PORT_HTTPS=443 ``` -See [Configuration](../installation/configuration) to change the internal ports. Be sure to run `docker-compose up -d` to rebuild with the new port numbers. +See [Configuration](../installation/configuration) to change the internal ports. Be sure to run `docker compose up -d` to rebuild with the new port numbers. ## Startup @@ -90,8 +90,8 @@ This will not give any advantages. It will cause problems with OAuth and SAML au Afterwards, run these commands to finish: ```shell -docker-compose pull -docker-compose up -d +docker compose pull +docker compose up -d ``` The `docker-compose.yml` file statically references the latest version available at the time of downloading the compose file. Each time you upgrade to a newer version of authentik, you download a new `docker-compose.yml` file, which points to the latest available version. For more information, refer to the **Upgrading** section in the [Release Notes](../releases). diff --git a/website/docs/releases/2024/v2024.1.md b/website/docs/releases/2024/v2024.1.md index 4552ee0cfb..fe82074cea 100644 --- a/website/docs/releases/2024/v2024.1.md +++ b/website/docs/releases/2024/v2024.1.md @@ -92,7 +92,7 @@ To upgrade, download the new docker-compose file and update the Docker stack wit ``` wget -O docker-compose.yml https://goauthentik.io/version/2024.1/docker-compose.yml -docker-compose up -d +docker compose up -d ``` The `-O` flag retains the downloaded file's name, overwriting any existing local file with the same name. diff --git a/website/docs/releases/_template.md b/website/docs/releases/_template.md index 03877e90ea..01b65ea06a 100644 --- a/website/docs/releases/_template.md +++ b/website/docs/releases/_template.md @@ -17,7 +17,7 @@ To upgrade, download the new docker-compose file and update the Docker stack wit ``` wget -O docker-compose.yml https://goauthentik.io/version/xxxx.x/docker-compose.yml -docker-compose up -d +docker compose up -d ``` The `-O` flag retains the downloaded file's name, overwriting any existing local file with the same name. diff --git a/website/docs/troubleshooting/emails.md b/website/docs/troubleshooting/emails.md index b3909a49b2..d6ed9c1f5e 100644 --- a/website/docs/troubleshooting/emails.md +++ b/website/docs/troubleshooting/emails.md @@ -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 diff --git a/website/docs/troubleshooting/forward_auth/general.mdx b/website/docs/troubleshooting/forward_auth/general.mdx index 80c23651ce..e03feb2748 100644 --- a/website/docs/troubleshooting/forward_auth/general.mdx +++ b/website/docs/troubleshooting/forward_auth/general.mdx @@ -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`. diff --git a/website/docs/troubleshooting/ldap_source.md b/website/docs/troubleshooting/ldap_source.md index ee3f843efd..04ca172322 100644 --- a/website/docs/troubleshooting/ldap_source.md +++ b/website/docs/troubleshooting/ldap_source.md @@ -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 diff --git a/website/docs/troubleshooting/login.md b/website/docs/troubleshooting/login.md index 58930706d9..31f1420b70 100644 --- a/website/docs/troubleshooting/login.md +++ b/website/docs/troubleshooting/login.md @@ -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 diff --git a/website/docs/troubleshooting/missing_admin_group.md b/website/docs/troubleshooting/missing_admin_group.md index a1e612dfdd..632e63fb41 100644 --- a/website/docs/troubleshooting/missing_admin_group.md +++ b/website/docs/troubleshooting/missing_admin_group.md @@ -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 diff --git a/website/docs/troubleshooting/missing_permission.md b/website/docs/troubleshooting/missing_permission.md index 8257208d7f..713b58610e 100644 --- a/website/docs/troubleshooting/missing_permission.md +++ b/website/docs/troubleshooting/missing_permission.md @@ -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 diff --git a/website/integrations/services/paperless-ng/index.md b/website/integrations/services/paperless-ng/index.md index c482ab6397..eed82187c1 100644 --- a/website/integrations/services/paperless-ng/index.md +++ b/website/integrations/services/paperless-ng/index.md @@ -36,7 +36,7 @@ PAPERLESS_HTTP_REMOTE_USER_HEADER_NAME=HTTP_X_AUTHENTIK_USERNAME Authentik automatically sets this header when we use a proxy outpost. Now restart your container: -`docker-compose down && docker-compose up -d` +`docker compose down && docker compose up -d` ## authentik