Preview routers don't inherit source app @file middlewares and tls.options

Summary

Preview deployments generate a separate Traefik dynamic file, but preview websecure routers do not inherit source app @file middlewares and tls.options.

Why this matters

Many setups attach security and edge constraints as global file middlewares and TLS options (for example: Cloudflare-only middleware and specific client auth options). Those are present on the main app router but missing on the preview router, so previews can behave differently or fail behind hardened ingress setups.

Current behavior

• Source app websecure router has @file middlewares and tls.options
• Preview router is generated without inheriting those settings
• Result: security mismatch between prod/app and preview routes

Expected behavior

When creating preview websecure routers, Dokploy should inherit source app websecure:

• middlewares entries ending with @file
• tls.options

unless explicitly overridden in preview-specific logic.

Notes

This keeps preview behavior aligned with source app security defaults and avoids manual post-generation patching on every preview deployment.

Start by locating the preview dynamic-file generation and the code that builds preview websecure routers, then compare it with the source app router configuration. Trace how @file middlewares and tls.options are represented and inherited. Done means generated preview websecure routers retain those source settings unless preview-specific logic overrides them, with relevant tests or configuration checks passing.