{"repo":"Saturate/traefik-wordpress","free":true,"listed":false,"github":"https://github.com/Saturate/traefik-wordpress","clone":"git clone https://github.com/Saturate/traefik-wordpress.git","description":"Using Træfik as a reverse proxy with HTTPS, for WordPress and other apps as well.","language":null,"stars":23,"topics":["docker","https","wordpress","traefik","traefik-wordpress","docker-compose"],"license":"MIT","category":"deployment-docker-iac","readme_excerpt":"Traefik WordPress Example setup for running Traefik v3 as a reverse proxy in front of WordPress, with automatic Let's Encrypt TLS certificates. Prerequisites - Docker with the Compose plugin - A domain name pointing to your server Getting started 1. Create the shared network: 2. Configure and start Traefik: 3. Configure and start WordPress: www redirect The WordPress router only matches the exact WORDPRESS HOST value. If you need www.example.com to redirect to example.com , add these labels to the WordPress service: Adding more sites Add another service with traefik.enable=true labels and the web network. Traefik picks up new containers automatically. Each site needs its own router name and Host() rule. Dashboard The Traefik dashboard is available at https:// /dashboard/ (trailing slash required), protected by HTTP basic auth. Generate credentials with: Paste the output into TRAEFIK DASHBOARD AUTH in traefik/.env .","default_branch":null,"files":null,"tree":[],"storefront":"/r/Saturate","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/Saturate/traefik-wordpress/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}