feat(franken): add configuration and guide frankenphp.md

Author: kevariable

.env

@@ -15,7 +15,7 @@
 # https://symfony.com/doc/current/best_practices.html#use-environment-variables-for-infrastructure-configuration
 
 ###> symfony/framework-bundle ###
-APP_ENV=prod
+APP_ENV=local
 APP_SECRET=2ca64f8d83b9e89f5f19d672841d6bb8
 #TRUSTED_PROXIES=127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16
 #TRUSTED_HOSTS='^(localhost|example\.com)$'

README.md

@@ -358,17 +358,6 @@ for detailed autoloader optimization guidelines and best practices.
 | Franken Metrics       | http://localhost:2019/metrics | Caddy/FrankenPHP metrics (non-worker) |
 | Worker Metrics        | http://localhost:2020/metrics | Caddy/FrankenPHP metrics (worker)     |
 
-## Grafana Dashboard
-
-A detailed PHP-FPM and OPcache monitoring dashboard is available in Grafana. It includes:
-
-- PHP-FPM health, queue, and process metrics
-- Request rate, duration, and memory usage
-- OPcache hit ratio, memory, and script cache stats
-- JIT and interned strings monitoring
-- Alerts and color-coded panels for quick health checks
-
-**See [`grafana-dashboard.md`](grafana-dashboard.md) for a full description of all panels and dashboard features.**
 
 ## FrankenPHP Configuration
 
@@ -382,4 +371,16 @@ comparison and monitoring.
 - Caddy configuration and environment variables
 - Performance testing and monitoring
 - Troubleshooting guide
-- Resource optimization guidelines
+- Resource optimization guidelines
+
+## Grafana Dashboard
+
+A detailed PHP-FPM and OPcache monitoring dashboard is available in Grafana. It includes:
+
+- PHP-FPM health, queue, and process metrics
+- Request rate, duration, and memory usage
+- OPcache hit ratio, memory, and script cache stats
+- JIT and interned strings monitoring
+- Alerts and color-coded panels for quick health checks
+
+**See [`grafana-dashboard.md`](grafana-dashboard.md) for a full description of all panels and dashboard features.**

docker/Caddyfile

@@ -8,16 +8,16 @@
 		max_threads auto # Keep stable, no dynamic scaling
 
 		worker {
-			watch
-
+			# watch
 			file ./public/index.php
 			num 16 # 2 workers per CPU core (8 cores * 2) - optimal balance
 		}
 
-		php_ini {
-			opcache.enable 0
-			opcache.validate_timestamps 1
-		}
+        # php_ini {
+        #     opcache.preload ""
+        #     opcache.revalidate_freq 0
+        #     opcache.validate_timestamps 1
+        # }
 	}
 }
 

docs/images/franken-worker-controller-watch.png

@@ -129,6 +129,21 @@ the Caddyfile:
 
 open ./docker/Caddyfile file
 
+
+uncomment
+
+```bash
+# watch
+
+# php_ini {
+#     opcache.preload ""
+#     opcache.revalidate_freq 0
+#     opcache.validate_timestamps 1
+# }
+```
+
+so it will looks like this
+
 ```caddyfile
 	frankenphp {
 		num_threads 20 # Optimal: 16 workers + 4 handling threads
@@ -140,10 +155,19 @@ open ./docker/Caddyfile file
 			file ./public/index.php
 			num 16 # 2 workers per CPU core (8 cores * 2) - optimal balance
 		}
+		
+		php_ini opcache.preload ""
+        php_ini opcache.revalidate_freq 0
+        php_ini opcache.validate_timestamps 1
 	}
 ```
 
-uncomment `# watch`
+why ?
+
+watch → FrankenPHP auto-reloads when files change
+preload → Load files once; changes NOT detected
+revalidate_freq → How often to check files for changes
+validate_timestamps → Whether to check changes at all
 
 go to terminal
 
@@ -171,32 +195,39 @@ if you notice that we have format issue at the file we can run
 frankenphp fmt --overwrite --config=/etc/frankenphp/Caddyfile
 ```
 
-and reload the config 
+if you don't faced that issue then just continue command below
 
 ```bash
 frankenphp reload --config=/etc/frankenphp/Caddyfile
 ```
 
-Go to http://localhost:8081/, if you reload it will hard reload the browser
-
-### Important Considerations
+Go to http://localhost:8081/en/blog/, if you reload it will hard reload the browser
 
-- **Performance Impact**: File watching uses system resources (inotify on Linux)
-- **Production Warning**: Always disable `watch` in production for stability
-- **Large Projects**: Watching many files can impact performance
+now let's open file ./src/Controller/BlogController.php
 
-**Production Best Practice:**
+and uncommented 
 
-```caddyfile
-frankenphp {
-    worker {
-        file ./public/index.php
-        # watch  # Commented out for production
-        num 8   # Increase workers instead
-    }
+```php
+public function index(Request $request, int $page, string $_format, PostRepository $posts, TagRepository $tags): Response
+{
+    phpinfo();
+    
+    ... another code
 }
 ```
 
+then Go to http://localhost:8081/en/blog/ again, we notice that phpinfo page is render
+
+![img.png](docs/images/franken-worker-controller-watch.png)
+
+so now everytime you make changes on the php, twig files it will reflect on the browser
+
+### Important Considerations
+
+- **Performance Impact**: File watching uses system resources
+- **Production Warning**: Always disable `watch` in production for stability
+- **Large Projects**: Watching many files can impact performance
+
 ### Worker Metrics
 
 When `metrics` is enabled, worker information is exposed at the metrics endpoint:

frankenphp.md

@@ -51,7 +51,8 @@ final class BlogController extends AbstractController
     #[Cache(smaxage: 10)]
     public function index(Request $request, int $page, string $_format, PostRepository $posts, TagRepository $tags): Response
     {
-        dump('FF');
+        // phpinfo();
+
         $tag = null;
 
         if ($request->query->has('tag')) {