proxy/dynamic/vert-sablier.yaml

http:
  middlewares:
    sablier-vert:
      plugin:
        sablier:
          names: vert_app
          sablierUrl: http://sablier_app:10000
          sessionDuration: 1h
          dynamic:
            displayName: VERT File Converter
            theme: ghost

    vert-auth:
      basicAuth:
        users:
          - '{{ env "AUTH_USERS" }}'

    vert-compress:
      compress: {}

  services:
    vert-web-secure:
      loadBalancer:
        servers:
          - url: "http://vert_app:80"

  routers:
    vert-web-secure:
      rule: "Host(`vert.pivoine.art`)"
      service: vert-web-secure
      entryPoints:
        - web-secure
      middlewares:
        - sablier-vert
        - vert-auth
        - vert-compress
      tls:
        certResolver: resolver
feat: add HTTP auth and Sablier scale-to-zero to VERT stack Added authentication and scale-to-zero capabilities to VERT file converter service: Authentication: - Added HTTP Basic Auth middleware using VERT_AUTH_USERS - Auth middleware applied to web-secure router - Credentials configured via .env file (htpasswd format) Sablier Scale-to-Zero: - Added sablier.enable and sablier.group labels - Created proxy/dynamic/vert-sablier.yaml with Sablier middleware config - 1-hour session duration before automatic scale-down - Ghost theme with custom display name - Middleware chain: sablier-vert@file → auth → compress Configuration Updates: - Added VERT_SABLIER_ENABLED to arty.yml (default: true) - Updated CLAUDE.md with auth and Sablier documentation - Middleware order ensures Sablier wakes container before auth check Infrastructure: - Follows same pattern as Scrapy service for auth - Dynamic Traefik configuration for Sablier plugin - Container name: vert_app (referenced in Sablier config) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 17:22:48 +01:00			`http:`
			`middlewares:`
			`sablier-vert:`
			`plugin:`
			`sablier:`
			`names: vert_app`
			`sablierUrl: http://sablier_app:10000`
			`sessionDuration: 1h`
			`dynamic:`
			`displayName: VERT File Converter`
			`theme: ghost`
fix: move Sablier middleware to dynamic configuration Moved Sablier middleware from Docker labels to Traefik dynamic configuration to fix "unknown plugin type: sablier" error. Traefik plugins can only be used in dynamic file configuration, not in Docker labels. Changes: - Removed sablier-vert@file reference from Docker label middleware chain - Added complete router definition to proxy/dynamic/vert-sablier.yaml - Router includes full middleware chain: sablier-vert → vert-auth → compress - Kept sablier.enable and sablier.group labels for Sablier service discovery This allows Sablier to properly scale the container to zero while maintaining the middleware chain order through file-based configuration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 17:27:04 +01:00
fix: define VERT middlewares in file provider with environment variable Fixed "middleware does not exist" error for VERT by defining all middlewares in the file provider configuration instead of relying on Docker provider middlewares from a stopped container (Sablier scale-to-zero). Changes: - Added vert-auth middleware using AUTH_USERS environment variable - Added vert-compress middleware for gzip compression - Passed AUTH_USERS to Traefik container via environment section - Removed @docker suffixes from middleware references This ensures middlewares are always available, even when the VERT container is stopped by Sablier's dynamic scaling feature. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 18:41:08 +01:00			`vert-auth:`
			`basicAuth:`
			`users:`
fix: correct Go template syntax for AUTH_USERS variable 2025-11-06 19:01:10 +01:00			`- '{{ env "AUTH_USERS" }}'`
fix: define VERT middlewares in file provider with environment variable Fixed "middleware does not exist" error for VERT by defining all middlewares in the file provider configuration instead of relying on Docker provider middlewares from a stopped container (Sablier scale-to-zero). Changes: - Added vert-auth middleware using AUTH_USERS environment variable - Added vert-compress middleware for gzip compression - Passed AUTH_USERS to Traefik container via environment section - Removed @docker suffixes from middleware references This ensures middlewares are always available, even when the VERT container is stopped by Sablier's dynamic scaling feature. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 18:41:08 +01:00
			`vert-compress:`
			`compress: {}`

fix: define VERT service in file provider instead of referencing Docker provider Fixed "the service 'vert-web-secure@docker' does not exist" error by defining the service directly in the vert-sablier.yaml file provider configuration. Previously, the router was defined in the file provider but tried to reference a service from the Docker provider (@docker suffix), which caused a mismatch. Now both the router and service are defined in the same file provider, while still using Docker-based middlewares (auth, compression). Changes: - Added services.vert-web-secure with loadBalancer pointing to vert_app:80 - Changed router service reference from "vert-web-secure@docker" to "vert-web-secure" 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 18:35:01 +01:00			`services:`
			`vert-web-secure:`
			`loadBalancer:`
			`servers:`
			`- url: "http://vert_app:80"`

fix: move Sablier middleware to dynamic configuration Moved Sablier middleware from Docker labels to Traefik dynamic configuration to fix "unknown plugin type: sablier" error. Traefik plugins can only be used in dynamic file configuration, not in Docker labels. Changes: - Removed sablier-vert@file reference from Docker label middleware chain - Added complete router definition to proxy/dynamic/vert-sablier.yaml - Router includes full middleware chain: sablier-vert → vert-auth → compress - Kept sablier.enable and sablier.group labels for Sablier service discovery This allows Sablier to properly scale the container to zero while maintaining the middleware chain order through file-based configuration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 17:27:04 +01:00			`routers:`
			`vert-web-secure:`
			rule: "Host(`vert.pivoine.art`)"
fix: define VERT service in file provider instead of referencing Docker provider Fixed "the service 'vert-web-secure@docker' does not exist" error by defining the service directly in the vert-sablier.yaml file provider configuration. Previously, the router was defined in the file provider but tried to reference a service from the Docker provider (@docker suffix), which caused a mismatch. Now both the router and service are defined in the same file provider, while still using Docker-based middlewares (auth, compression). Changes: - Added services.vert-web-secure with loadBalancer pointing to vert_app:80 - Changed router service reference from "vert-web-secure@docker" to "vert-web-secure" 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 18:35:01 +01:00			`service: vert-web-secure`
fix: move Sablier middleware to dynamic configuration Moved Sablier middleware from Docker labels to Traefik dynamic configuration to fix "unknown plugin type: sablier" error. Traefik plugins can only be used in dynamic file configuration, not in Docker labels. Changes: - Removed sablier-vert@file reference from Docker label middleware chain - Added complete router definition to proxy/dynamic/vert-sablier.yaml - Router includes full middleware chain: sablier-vert → vert-auth → compress - Kept sablier.enable and sablier.group labels for Sablier service discovery This allows Sablier to properly scale the container to zero while maintaining the middleware chain order through file-based configuration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 17:27:04 +01:00			`entryPoints:`
			`- web-secure`
			`middlewares:`
			`- sablier-vert`
fix: define VERT middlewares in file provider with environment variable Fixed "middleware does not exist" error for VERT by defining all middlewares in the file provider configuration instead of relying on Docker provider middlewares from a stopped container (Sablier scale-to-zero). Changes: - Added vert-auth middleware using AUTH_USERS environment variable - Added vert-compress middleware for gzip compression - Passed AUTH_USERS to Traefik container via environment section - Removed @docker suffixes from middleware references This ensures middlewares are always available, even when the VERT container is stopped by Sablier's dynamic scaling feature. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 18:41:08 +01:00			`- vert-auth`
			`- vert-compress`
fix: move Sablier middleware to dynamic configuration Moved Sablier middleware from Docker labels to Traefik dynamic configuration to fix "unknown plugin type: sablier" error. Traefik plugins can only be used in dynamic file configuration, not in Docker labels. Changes: - Removed sablier-vert@file reference from Docker label middleware chain - Added complete router definition to proxy/dynamic/vert-sablier.yaml - Router includes full middleware chain: sablier-vert → vert-auth → compress - Kept sablier.enable and sablier.group labels for Sablier service discovery This allows Sablier to properly scale the container to zero while maintaining the middleware chain order through file-based configuration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-11-06 17:27:04 +01:00			`tls:`
			`certResolver: resolver`