Raúl Sánchez

@claflico , sorry about long delay answer. More than happy to accept your PR, please, feel free to submit it. I've created a new branch to v.1 and master branch...

By the moment, you could overwrite docker ssl key/cert with env variable `TRAEFIK_SSL_KEY` and `TRAEFIK_SSL_CRT`. But sure, may be a good alternative use key generator. :)

Hey @joshuacox ... Obviously, to use traefik with acme enabled in production, a better persistence solution for ssl certs is needed. Sharing `/opt/traefik/acme` doesn't seem a good idea, due to...

@joshuacox , which kv store is not a problem, which ever could work just fine... I guess that all are already on the rancher community catalog... :) I've took a...

I've published a version with the optional acme volume from another container at my repo... I've used go templating in docker-compose.yml.tpl for create the traefik volume only if enable acme...

Merged into community catalog.... https://github.com/rancher/community-catalog/pull/500

Hi guys, @joshuacox, Rancher v2.0 is in alpha state, and eventually catalog could be eventually outdated but not deprecated, we'll update all packages to this version. In rancher v2.0 you...

@hermsi1337, the main difference is that with rancher integration, all services could get letsencrypt certificates, not just traefik. I already wrote in my previous comment, that this package doesn't support...

So busy....Pull requests are very welcomed.. ;)

@jonahlau to make letsencrypt stack work with this, traefik acme support needs to be disabled. Take a look to https://www.digitalocean.com/community/tutorials/how-to-secure-your-rancher-web-app-with-let-s-encrypt-on-ubuntu-16-04