kelin
f318170d02
Changes: - Reviewed all docker-compose files to identify required variables - Updated all .env.example files to include ONLY variables used in their respective compose files - Changed all placeholder values to empty strings for cleaner configuration - Fixed variable name inconsistency: DOWNLOADS_DIR -> DOWNLOAD_DIR (to match main .env) - Removed unnecessary variables that aren't used by the compose files All .env.example files now: - Contain only the variables actually used in the stack - Have empty values instead of example placeholders - Match the variable names used in docker-compose files This ensures clean, minimal .env files for each stack without any extraneous variables or confusing placeholder values.
Sablier Stack
This stack deploys Sablier, a service that provides lazy loading (on-demand startup) for Docker containers.
Overview
Sablier monitors Docker containers and can automatically start them when they receive traffic through Traefik, then stop them after a period of inactivity. This is useful for:
- Reducing resource usage on servers with limited RAM/CPU
- Managing seasonal or infrequently-used services
- Extending the capacity of small servers (like Raspberry Pi)
Multi-Server Architecture
Each server in your homelab should have its own Sablier instance:
- Core Server: Manages lazy loading for core services
- Remote Servers: Each runs Sablier to control local containers
Sablier only connects to the local Docker socket (/var/run/docker.sock) on its own server.
Features
- Web Dashboard: Access at
https://sablier.yourdomain.duckdns.org - Protected by Authelia: SSO authentication required
- Local Control: Only manages containers on the same server
- Traefik Integration: Uses Traefik middlewares for automatic container startup
Usage
Enable Lazy Loading on a Container
Add these labels to any service in your docker-compose files:
services:
myservice:
image: myapp:latest
labels:
- "traefik.enable=true"
- "traefik.http.routers.myservice.rule=Host(`myservice.yourdomain.duckdns.org`)"
- "traefik.http.routers.myservice.entrypoints=websecure"
- "traefik.http.routers.myservice.tls=true"
- "traefik.http.routers.myservice.middlewares=sablier-myservice@docker"
# Sablier middleware configuration
- "traefik.http.middlewares.sablier-myservice.plugin.sablier.names=myservice"
- "traefik.http.middlewares.sablier-myservice.plugin.sablier.sablierUrl=http://sablier:10000"
- "traefik.http.middlewares.sablier-myservice.plugin.sablier.sessionDuration=5m"
Configuration Options
names: Container name(s) to manage (comma-separated for multiple)sablierUrl: URL of the Sablier service (usehttp://sablier:10000for local)sessionDuration: How long to keep the container running after last request (e.g.,5m,1h)
Deployment
This stack is automatically deployed:
- On the core server after core infrastructure deployment
- On remote servers during remote server setup
Manual deployment:
cd /opt/stacks/sablier
docker compose up -d
Resources
- CPU: ~10-20 MB RAM per instance
- Storage: Minimal (~50 MB)
- Network: Internal Docker network only