Glebaster/forum
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix command to run containers (#512)

Browse Source 
* docs(production): fix command to run containers

The commands were pointing to a `docker-compose.yml` file that doesn't exist. It's `compose.yaml` now.

* docs(tls): update config file name

* docs(extra-services): update config file name
This commit is contained in:
Cyrille Perois 2023-11-20 12:51:54 +01:00 committed by GitHub
parent d82099b49d
commit f74c8c6cb8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/extra-services.md
View File

@ -1,7 +1,7 @@
# Support for Extra Services # Support for Extra Services
Symfony Docker is extensible. When you install a compatible Composer package using Symfony Flex, Symfony Docker is extensible. When you install a compatible Composer package using Symfony Flex,
the recipe will automatically modify the `Dockerfile` and `docker-compose.yml` to fulfill the requirements of this package. the recipe will automatically modify the `Dockerfile` and `compose.yaml` to fulfill the requirements of this package.
The currently supported packages are: The currently supported packages are:

4
docs/production.md
View File

@ -61,7 +61,7 @@ Go into the directory containing your project (`<project-name>`), and start the
SERVER_NAME=your-domain-name.example.com \ SERVER_NAME=your-domain-name.example.com \
APP_SECRET=ChangeMe \ APP_SECRET=ChangeMe \
CADDY_MERCURE_JWT_SECRET=ChangeThisMercureHubJWTSecretKey \ CADDY_MERCURE_JWT_SECRET=ChangeThisMercureHubJWTSecretKey \
docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d --wait docker compose -f compose.yaml -f compose.prod.yaml up -d --wait
``` ```
Be sure to replace `your-domain-name.example.com` by your actual domain name and to set the values of `APP_SECRET`, `CADDY_MERCURE_JWT_SECRET` to cryptographically secure random values. Be sure to replace `your-domain-name.example.com` by your actual domain name and to set the values of `APP_SECRET`, `CADDY_MERCURE_JWT_SECRET` to cryptographically secure random values.
@ -77,7 +77,7 @@ Alternatively, if you don't want to expose an HTTPS server but only an HTTP one,
SERVER_NAME=:80 \ SERVER_NAME=:80 \
APP_SECRET=ChangeMe \ APP_SECRET=ChangeMe \
CADDY_MERCURE_JWT_SECRET=ChangeThisMercureHubJWTSecretKey \ CADDY_MERCURE_JWT_SECRET=ChangeThisMercureHubJWTSecretKey \
docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d --wait docker compose -f compose.yaml -f compose.prod.yaml up -d --wait
``` ```
## Deploying on Multiple Nodes ## Deploying on Multiple Nodes

2
docs/tls.md
View File

@ -26,7 +26,7 @@ For instance, to use self-signed certificates created with [mkcert](https://gith
`mkdir frankenphp/certs -p` `mkdir frankenphp/certs -p`
3. Generate the certificates for your local host (example: "server-name.localhost"): 3. Generate the certificates for your local host (example: "server-name.localhost"):
`mkcert -cert-file frankenphp/certs/tls.pem -key-file frankenphp/certs/tls.key "server-name.localhost"` `mkcert -cert-file frankenphp/certs/tls.pem -key-file frankenphp/certs/tls.key "server-name.localhost"`
4. Add these lines to the `./docker-compose.override.yml` file about `CADDY_EXTRA_CONFIG` environment and volume for the `php` service : 4. Add these lines to the `./compose.override.yaml` file about `CADDY_EXTRA_CONFIG` environment and volume for the `php` service :
```diff ```diff
php: php:
environment: environment: