skills.rest
Innei
InneiCOMMUNITY
Explore all skills by this author →
Website𝕏@__oQueryGitHub

dokploy-traefik-traffic-split

Orchestrate weight-driven canary traffic splits for two backends behind a Dokploy-managed domain.

61|1|Updated Apr 2, 2026
Search Tags:#routing#canary#weighting#traefik#dokploy#path-prefix#spa-migration
One-click install
npx skills add https://github.com/Innei/SKILL --skill dokploy-traefik-traffic-split
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dokploy-traefik-traffic-split
Source: https://github.com/Innei/SKILL/tree/main/skills/infrastructure/dokploy-traefik-traffic-split
Command: npx skills add https://github.com/Innei/SKILL --skill dokploy-traefik-traffic-split

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When migrating or testing frontend backends under a single Dokploy-managed domain, SPA asset paths and cookie-based stickiness can cause inconsistent routing and 404s. This skill provides a path-aware Traefik configuration that preserves user sessions while safely splitting traffic between two backends.

Core Features & Use Cases

  • Path-prefix routers at higher priority bypass the weighted service for document-like requests (HTML, CSS, JS, assets), eliminating SPA-asset traps.
  • Four-phase workflow (backup → dry-run on a canary host → roll to prod → quick rollback) for safe migrations and experiments.
  • Clear guidance for SPA migrations and long-running A/B tests on Dokploy-managed domains with automated verification.

Quick Start

Create the canary Traefik YAML for your host and deploy it to the Dokploy server, then verify the weighted split using canary.yourdomain.com.

Frequently Asked Questions about dokploy-traefik-traffic-split

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split traffic between two backends on a single Dokploy domain without breaking SPA assets?▼

You can split traffic by applying a path-aware Traefik configuration using path-prefix routers at a higher priority to bypass weighted services for document-like requests, preventing SPA asset 404s.

What is weighted canary routing and when should I use it for SPA migrations?▼

Weighted canary routing progressively shifts traffic between two backends. It is needed for SPA migrations or A/B testing where asset paths differ, ensuring user session consistency while testing new deployments.

How do I set up a canary rollout for Traefik on Dokploy step by step?▼

Set up canary routing by following a four-phase workflow: back up existing configurations, dry-run on a canary host, roll out to production, and execute a quick rollback if verification fails.

Why does cookie-based stickiness cause 404 errors during frontend A/B testing?▼

Cookie-based stickiness causes 404s when SPA asset paths differ between backends, trapping document-style requests in the wrong service. A higher-priority path-prefix router setup guards against this issue.

Does Dokploy support path-prefix routers for weighted traffic splitting?▼

Yes, Dokploy supports this through Traefik configurations. Path-prefix routers at higher priority bypass the weighted service for document-like requests to eliminate SPA-asset traps during migrations.

What are the limitations of using weighted routing for single-page application migrations?▼

Weighted routing alone can cause inconsistent routing and 404s if SPA asset paths differ. It requires path-prefix routers to bypass weighted services for document requests, avoiding cookie stickiness issues.

Related Skills

Explore More Software Engineering Skills→
evolv3-aievolv3-ai
1

admin-app-coolify

Install and configure Coolify on Ubuntu servers with Docker and Traefik.

Official
Advanced
shafibabarshafibabar
1

canary-deployment

Coordinate Linkerd traffic splits and Argo Rollouts gates for canary deployments.

Community
Advanced
tdcaretdcare
1

salvo-routing

Configure nested Salvo routers with path parameters and Hoop middleware for Rust APIs.

Community
Advanced
NevaberryNevaberry
22

traefik-knowledge-patch

Update Traefik v3.1 through v3.6.9 configurations for breaking changes and new features.

Official
Intermediate