🔧 extend nginx server config for CORS

Author: FabianWilms

personalization-webcomponents/docker/nginx/files.conf

@@ -1,10 +1,17 @@
-location /src/ {
+location / {
+  add_header 'Access-Control-Allow-Origin' $allow_origin;
+  add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS' always;
+
+  location /src/ {
     expires 365d;
-    add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS' always;
-    add_header Cache-Control 'public, no-transform';
-}
+    add_header 'Access-Control-Allow-Origin' $allow_origin;
+    add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS' always;
+    add_header Cache-Control "public, no-transform";
+  }
 
-location ~ ^/loader-.*\.js$ {
+  location ~ ^/loader-.*\.js$ {
+    add_header 'Access-Control-Allow-Origin' $allow_origin;
     add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS' always;
     add_header Cache-Control 'no-cache';
-}
+  }
+}

personalization-webcomponents/docker/nginx/server.conf

@@ -0,0 +1,15 @@
+map $http_origin $allow_origin {
+    # Obviously for muenchen.de
+    ~^https?://(.*\.)?muenchen.de(:\d+)?$ $http_origin;
+
+    # Test-Site for Magnolia is not under muenchen.de-Domain
+    ~^https?://(.*\.)?swm.de(:\d+)?$ $http_origin;
+
+    # And the Header of muenchen.de has it's testpage on this domain...
+    ~^https?://(.*\.)?platformsh.site(:\d+)?$ $http_origin;
+
+    # If we need to debug something from our local machines.
+    ~^https?://(.*\.)?localhost(:\d+)?$ $http_origin;
+
+    default "";
+}

personalization-webcomponents/vite.config.ts

@@ -33,6 +33,7 @@ export default defineConfig(({ mode }) => {
     },
     build: {
       manifest: true, // required for post build logic in 'processes' folder
+      minify: true,
       rollupOptions: {
         input: {
           "checklist-detail": "./src/checklist-detail-webcomponent.ts",