Linked Data Frontend (LDF) Migration Guide

This workaround consists of the following steps:

1. Inject Environment Variables: Add the following environment variables to the poolparty service block in your docker-compose.yaml to relax the container's internal restrictions.

   services:
     poolparty:
       # ... other configurations ...
       environment:
         - _POOLPARTY_LDF_SCRIPT_SRC="* data: blob: 'unsafe-inline' 'unsafe-eval'"
         - _POOLPARTY_LDF_STYLE_SRC="* data: blob: 'unsafe-inline'"
         - _POOLPARTY_LDF_IMG_SRC="* data: blob:"
         - _POOLPARTY_LDF_CONNECT_SRC="* data: blob: ws: wss:"

   For details on how to specify Graph Modeling properties as environment variables, refer to the section on Environment Variables in the Graph Modeling Configuration Properties page.

2. Force CSP Rewrite at Proxy Level: Edit your Nginx proxy configuration file (typically located at /compose-files/compose-files/files/nginx/includes/poolparty.conf) to include the following block to override headers for LDF paths:

   location ~ ^/[^/]+\.(html|rdf|owl|xml|n3|ttl|ttls|trig|trigs|trix|nq|brf|nt|rj|jsonld|visual|map|not_found|nicht_gefunden)$ {
      proxy_pass http://poolparty:8081;
   
      proxy_set_header Host              $host;
      proxy_set_header X-Real-IP         $remote_addr;
      proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_set_header X-Forwarded-Host  $host;
      proxy_set_header X-Forwarded-Port  $server_port;
   
      # Override CSP for LDF pages only (INSECURE; allows inline scripts/styles)
      proxy_hide_header Content-Security-Policy;
      proxy_hide_header Content-Security-Policy-Report-Only;
      add_header Content-Security-Policy "default-src 'none'; style-src 'self' * data: blob: 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.googleapis.com https://fonts.gstatic.com; img-src 'self' * data: blob:; script-src 'self' * data: blob: 'unsafe-inline' 'unsafe-eval'; connect-src 'self' * data: blob: ws: wss:;" always;
   }

3. Migrate Assets to the Docker Volume: Assuming a docker-compose setup where your legacy custom LDF is at /opt/poolparty9/data/frontendRoot/custom and the target named volume is compose-files_poolparty_data, populate the volume using an ephemeral container:

   docker run --rm \
     -v compose-files_poolparty_data:/dest \
     -v /opt/poolparty9/data/frontendRoot/custom:/src:ro \
     alpine sh -lc 'rm -rf /dest/data/frontendRoot/custom && mkdir -p /dest/data/frontendRoot/custom && cp -a /src/. /dest/data/frontendRoot/custom/'

4. Restart Services: Apply all changes by restarting your services.

   docker compose -f docker-compose.yaml -f addons.yaml up -d poolparty