fix: generate-certificates namespace

.castor/docker.php

@@ -150,7 +150,7 @@ function destroy(
     fs()->remove($files);
 }
 
-#[AsTask(description: 'Generates SSL certificates (with mkcert if available or self-signed if not)', namespace: '')]
+#[AsTask(description: 'Generates SSL certificates (with mkcert if available or self-signed if not)')]
 function generate_certificates(
     #[AsOption(description: 'Force the certificates re-generation without confirmation', shortcut: 'f')]
     bool $force = false,

README.dist.md

@@ -72,7 +72,7 @@ installed on your computer - see below).
 
 HTTPS is supported out of the box. SSL certificates are not versioned and will
 be generated the first time you start the infrastructure (`castor start`) or if
-you run `castor infra:generate-certificates`.
+you run `castor docker:generate-certificates`.
 
 If you have `mkcert` installed on your computer, it will be used to generate
 locally trusted certificates. See [`mkcert` documentation](https://github.com/FiloSottile/mkcert#installation)
@@ -83,7 +83,7 @@ If you don't have `mkcert`, then self-signed certificates will instead be
 generated with openssl. You can configure [infrastructure/docker/services/router/openssl.cnf](infrastructure/docker/services/router/openssl.cnf)
 to tweak certificates.
 
-You can run `castor infra:generate-certificates --force` to recreate new certificates
+You can run `castor docker:generate-certificates --force` to recreate new certificates
 if some were already generated. Remember to restart the infrastructure to make
 use of the new certificates with `castor up` or `castor start`.