Move template assets to .env-driven generation.

Site metadata, images, favicons, and YouTube settings are now configured via .env and rendered from HTML/manifest templates at dev or container startup.

Co-authored-by: Cursor <cursoragent@cursor.com>

dev.sh

@@ -10,22 +10,22 @@ if [[ ! -f .env ]]; then
   echo "Utworzono .env z .env.example"
 fi
 
-generate_config() {
+generate_from_env() {
   set -a
   # shellcheck disable=SC1091
   source .env
   set +a
-  ./generate-config.sh config.js
+  chmod +x generate-from-env.sh
+  ./generate-from-env.sh .
 }
 
 case "${1:-up}" in
   up)
-    chmod +x generate-config.sh
-    generate_config
+    generate_from_env
     $COMPOSE up -d
     echo ""
     echo "Dev server: http://localhost:${FRONTEND_PORT:-8082}"
-    echo "Edytuj pliki → F5 w przeglądarce (bez rebuildu)."
+    echo "Edytuj .env → ./dev.sh config → F5 w przeglądarce."
   ;;
   down)
     $COMPOSE down
@@ -34,12 +34,12 @@ case "${1:-up}" in
     $COMPOSE logs -f
   ;;
   restart)
-    generate_config
+    generate_from_env
     $COMPOSE restart
   ;;
   config)
-    generate_config
-    echo "Wygenerowano config.js (POST_VIDEO_REDIRECT_URL z .env)."
+    generate_from_env
+    echo "Wygenerowano index.html, site.webmanifest i config.js z .env."
   ;;
   reload-nginx)
     docker exec slavic-pulse-com-frontend nginx -s reload