Traefik Config Example
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
As I use Traefik proxy and I'm certainly not the only one.
Here is a config example :
```yaml
---
services:
server:
image: 0xfurai/peekaping-server:latest
container_name: peekaping-server
restart: unless-stopped
depends_on:
migrate:
condition: service_completed_successfully
environment:
DB_TYPE: sqlite
DB_NAME: /app/data/peekaping.db
MODE: prod
TZ: ${TZ}
volumes:
- peekaping-db:/app/data
networks:
- traefik-net
labels:
- "traefik.enable=true"
- "traefik.http.routers.peekaping-api.entrypoints=websecure"
- "traefik.http.routers.peekaping-api.rule=Host(`${TRAEFIK_HOST}`) && (PathPrefix(`/api/`) || PathPrefix(`/socket.io/`))"
- "traefik.http.routers.peekaping-api.service=peekaping-api-svc"
- "traefik.http.routers.peekaping-api.tls=true"
- "traefik.http.services.peekaping-api-svc.loadbalancer.server.port=8034"
web:
image: 0xfurai/peekaping-web:latest
container_name: peekaping-web
depends_on:
- server
restart: unless-stopped
networks:
- traefik-net
labels:
- "traefik.enable=true"
- "traefik.http.routers.peekaping-web}.entrypoints=websecure"
- "traefik.http.routers.peekaping-web.rule=Host(`${TRAEFIK_HOST}`)"
- "traefik.http.routers.peekaping-web.service=peekaping-web-svc"
- "traefik.http.routers.peekaping-web.tls=true"
- "traefik.http.services.peekaping-web-svc.loadbalancer.server.port=80"
migrate:
image: 0xfurai/peekaping-migrate:latest
restart: "no"
network_mode: none
environment:
DB_TYPE: sqlite
DB_NAME: /app/data/peekaping.db
volumes:
- peekaping-db:/app/data
volumes:
peekaping-db:
name: peekaping-db
networks:
traefik-net:
external: true
```
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue provides a full Traefik configuration example in YAML for Docker Compose. To incorporate this, locate the project's documentation or examples directory, likely under `docs/` or in a `docker-compose.yml` example file. Verify the configuration matches the project's service ports and network setup. Adding this as a new example file or section in existing deployment docs would complete the task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, yaml
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 75/100