Fix: Publishing assets on prod

docker/entrypoint.sh

@@ -41,19 +41,17 @@ echo "[entrypoint] Caches cleared"
 
 php artisan storage:link --quiet 2>/dev/null || true
 
-if [ "$APP_ENV" != "production" ]; then
-    # Dev-only for the same reason as the composer step above — production's
-    # image already has these published at build time.
-    php artisan vendor:publish --tag=core-assets --force --ansi --quiet
-    php artisan vendor:publish --tag=public --force --ansi --quiet
-    php artisan filament:assets --ansi --quiet
+# Dev-only for the same reason as the composer step above — production's
+# image already has these published at build time.
+php artisan vendor:publish --tag=core-assets --force --ansi --quiet
+php artisan vendor:publish --tag=public --force --ansi --quiet
+php artisan filament:assets --ansi --quiet
 
-    # No --force: core-views publishes editable Blade templates (order
-    # notification emails), meant to be hand-customized per app — unlike
-    # core-assets above, republishing must not silently wipe local edits.
-    # Only fills in the vendor/core views directory if it doesn't exist yet.
-    php artisan vendor:publish --tag=core-views --ansi --quiet
-fi
+# No --force: core-views publishes editable Blade templates (order
+# notification emails), meant to be hand-customized per app — unlike
+# core-assets above, republishing must not silently wipe local edits.
+# Only fills in the vendor/core views directory if it doesn't exist yet.
+php artisan vendor:publish --tag=core-views --ansi --quiet
 
 # Everything below is universal, in both dev and production: application STATE
 # that must be current on every boot, not a build-time concern composer/assets