docs: update artifacts

Author: 7-zete-7

docs/mysql.md

@@ -10,7 +10,7 @@ Change the database image to use MySQL instead of PostgreSQL in `compose.yaml`:
 
 ```diff
 ###> doctrine/doctrine-bundle ###
--   image: postgres:${POSTGRES_VERSION:-15}-alpine
+-   image: postgres:${POSTGRES_VERSION:-16}-alpine
 +   image: mysql:${MYSQL_VERSION:-8}
     environment:
 -     POSTGRES_DB: ${POSTGRES_DB:-app}

docs/options.md

@@ -60,7 +60,7 @@ You can also customize the `Caddyfile` by using the following environment variab
 | `CADDY_SERVER_LOG_OPTIONS`      | the [server log options block](https://caddyserver.com/docs/caddyfile/directives/log), one per line                                                                                     |                           |
 | `SERVER_NAME`                   | the server name or address                                                                                                                                                              | `localhost`               |
 | `FRANKENPHP_CONFIG`             | a list of extra [FrankenPHP directives](https://frankenphp.dev/docs/config/#caddyfile-config), one per line                                                                             | `import worker.Caddyfile` | 
-| `MERCURE_TRANSPORT_URL`         | the value passed to the `transport_url` directive                                                                                                                                       | `bolt://mercure.db`       |
+| `MERCURE_TRANSPORT_URL`         | the value passed to the `transport_url` directive                                                                                                                                       | `bolt:///data/mercure.db` |
 | `MERCURE_PUBLISHER_JWT_KEY`     | the JWT key to use for publishers                                                                                                                                                       |                           |
 | `MERCURE_PUBLISHER_JWT_ALG`     | the JWT algorithm to use for publishers                                                                                                                                                 | `HS256`                   |
 | `MERCURE_SUBSCRIBER_JWT_KEY`    | the JWT key to use for subscribers                                                                                                                                                      |                           |

docs/tls.md

@@ -34,7 +34,7 @@ For instance, to use self-signed certificates created with [mkcert](https://gith
         # ...
       volumes:
     +    - ./frankenphp/certs:/etc/caddy/certs:ro
-        - ./public:/app/public:ro
+        # ...
     ```
 5. Restart your `php` service
 

docs/xdebug.md

@@ -49,23 +49,28 @@ You can now use the debugger!
 ## Debugging with Xdebug and VScode
 
 1. Install necessery [PHP extension for VScode](https://marketplace.visualstudio.com/items?itemName=DEVSENSE.phptools-vscode).
-2. Add [debug configuration](https://code.visualstudio.com/docs/editor/debugging#_launch-configurations) into your `.vscode\launch.json` file.
+2. Add [debug configuration](https://code.visualstudio.com/docs/debugtest/debugging-configuration#_launch-configurations) into your `.vscode\launch.json` file.
 
     Example:
     
     ```
     {
-        "name": "Listen for Xdebug",
-        "type": "php",
-        "request": "launch",
-        "port": 9003,
-        "pathMappings": {
-            "/app": "${workspaceFolder}"
-        }
+        "version": "0.2.0",
+        "configurations": [
+            {
+                "name": "Listen for Xdebug",
+                "type": "php",
+                "request": "launch",
+                "port": 9003,
+                "pathMappings": {
+                    "/app": "${workspaceFolder}"
+                }
+            }
+        ]
     }
     ```
     
-3. Use [Run and Debug](https://code.visualstudio.com/docs/editor/debugging) options and run  `Listen for Xdebug` command to listen for upcomming connections with [the **Xdebug extension**](https://xdebug.org/docs/step_debug#browser-extensions) installed and active.
+3. Use [Run and Debug](https://code.visualstudio.com/docs/debugtest/debugging#_start-a-debugging-session) options and run  `Listen for Xdebug` command to listen for upcomming connections with [the **Xdebug extension**](https://xdebug.org/docs/step_debug#browser-extensions) installed and active.
 
 ## Troubleshooting