traefikAvoid common Traefik mistakes — router priority, TLS configuration, Docker labels syntax, and middleware ordering.
Install via ClawdBot CLI:
clawdbot install ivangdavila/traefikrule AND service — missing either = not workingpriority to overrideHost() is case-insensitive — Host(\example.com\) matches Example.comHost(\a.com\) || Host(\b.com\) — OR logicdeploy.labels for SwarmHost(\example.com\) with escapingtraefik.enable=true — if exposedByDefault=falsetraefik.http.services.myservice.loadbalancer.server.port=80websecure needs TLS config — otherwise plain HTTP on 443certificatesResolvers.myresolver.acme.email required — registration fails withouttls=true on router activates TLS — tls.certresolver=myresolver for auto-certcaServer to staging URL, avoids rate limits--entrypoints.web.address=:80entryPoints=web,websecure — comma-separated listmiddlewares=auth,compressstripPrefix, redirectScheme, basicAuth, rateLimithtpasswd format — escape $ in Docker Compose with $$loadbalancer.server.port when container exposes multiple — Traefik can't guesshealthcheck.path=/health — removes unhealthy from rotationloadbalancer.sticky.cookie.name=srv_id — for stateful appstraefik.docker.network with multiple networks — Traefik picks wrong oneapi.insecure=true is dangerous in productionwatch=true for hot reload — otherwise restart Traefik on changes--log.level=DEBUG for troubleshooting — verbose but helpful--api.insecure=true for local dev only — secure with auth in productionGenerated Mar 1, 2026
Deploying Traefik as an API gateway for microservices running in Docker containers. Developers need to configure router rules for different services, set up TLS with Let's Encrypt for secure communication, and implement middleware like rate limiting and authentication to protect backend services.
Hosting multiple client websites on a shared infrastructure using Traefik as a reverse proxy. Configuration involves setting up router priorities for domain-based routing, implementing TLS certificates for each client domain, and using Docker labels to automatically expose new client containers as they're deployed.
Creating a centralized access point for internal development tools and services. Teams need to configure entrypoints for HTTP/HTTPS redirection, set up basic authentication middleware for security, and use file provider alongside Docker provider to include external services not running in containers.
Implementing Traefik as a load balancer for an e-commerce application with multiple backend instances. Configuration requires sticky sessions for shopping cart functionality, health checks to remove unhealthy instances, and proper TLS setup with certificate resolvers for secure checkout pages.
Using Traefik to route traffic to different deployment environments (dev, staging, production) based on hostnames or paths. Teams must configure router rules with proper priorities, set up middleware chains for request processing, and ensure TLS configuration works correctly across all environments.
Offering professional services to configure and maintain Traefik setups for clients. Revenue comes from monthly retainer fees for ongoing configuration management, troubleshooting, and optimization of router rules, TLS certificates, and middleware chains.
Providing training courses and certification programs for DevOps teams learning to implement Traefik. Revenue streams include course fees, certification exams, and corporate training packages focused on avoiding common configuration mistakes and best practices.
Selling pre-configured Traefik templates, Docker Compose files, and configuration generators. Revenue is generated through one-time purchases or subscriptions for access to template libraries that help users quickly set up common scenarios with proper TLS, middleware, and routing configurations.
💬 Integration Tip
Start with Docker provider for containerized services, then add file provider for external resources. Always test with staging ACME certificates before production deployment to avoid rate limits.
Automatically update Clawdbot and all installed skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.
Full desktop computer use for headless Linux servers. Xvfb + XFCE virtual desktop with xdotool automation. 17 actions (click, type, scroll, screenshot, drag,...
Essential Docker commands and workflows for container management, image operations, and debugging.
Tool discovery and shell one-liner reference for sysadmin, DevOps, and security tasks. AUTO-CONSULT this skill when the user is: troubleshooting network issues, debugging processes, analyzing logs, working with SSL/TLS, managing DNS, testing HTTP endpoints, auditing security, working with containers, writing shell scripts, or asks 'what tool should I use for X'. Source: github.com/trimstray/the-book-of-secret-knowledge
Deploy applications and manage projects with complete CLI reference. Commands for deployments, projects, domains, environment variables, and live documentation access.
Monitor topics of interest and proactively alert when important developments occur. Use when user wants automated monitoring of specific subjects (e.g., product releases, price changes, news topics, technology updates). Supports scheduled web searches, AI-powered importance scoring, smart alerts vs weekly digests, and memory-aware contextual summaries.