fix: remove ingress rewrite-target and dynamic env generator for helm2

Dockerfile

@@ -80,6 +80,9 @@ RUN echo 'server { \
     } \
 }' > /etc/nginx/sites-available/default
 
+# ... (bagian atas Dockerfile tetap sama) ...
+
 EXPOSE 80
 
-CMD ["sh", "-c", "redis-server --daemonize yes && php-fpm -D && exec nginx -g 'daemon off;'"]
+# Script startup: Buat .env dari variabel environment Helm jika .env belum ada, lalu jalankan service
+CMD ["sh", "-c", "env | grep -E '^(APP_|DB_|MYSQL_|ORA_|REDIS_|MAIL_|SESSION_|SOA_)' > /var/www/html/.env && redis-server --daemonize yes && php-fpm -D && exec nginx -g 'daemon off;'"]

helm/sidata/values.yaml

@@ -15,12 +15,12 @@ ingress:
   enabled: true
   className: nginx
   annotations:
-    # KITA AKTIFKAN KEMBALI REWRITE DI SINI
-    nginx.ingress.kubernetes.io/use-regex: "true"
-    nginx.ingress.kubernetes.io/rewrite-target: /$2
+    # HAPUS rewrite-target agar URL /sidata diteruskan utuh ke Pod
+    # Nginx di dalam Pod kita sudah punya 'location /sidata'
+    nginx.ingress.kubernetes.io/ssl-redirect: "false"
   host: dashboard-bpkd.drc-bpkd.data-center.id
-  path: /sidata(/|$)(.*)
-  pathType: ImplementationSpecific
+  path: /sidata
+  pathType: Prefix
 
 env:
   APP_NAME: "SIDATA"