Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grayed out bindings that already have a Let's Encrypt certificate #264

Open
koakenred opened this issue Mar 1, 2018 · 3 comments
Open

Comments

@koakenred
Copy link

Is it possible to grayed out bindings that already have a Let's Encrypt Certificate. We have a lot of bindings that need a certificate so this function would be very handy.

@webprofusion-chrisc
Copy link
Contributor

Great idea! Yes, it's possible. Perhaps the option could be to hide (filter out) hostnames managed by another item. That way the list will get shorter/easier to manage as you go.

Are you just using Certify or are you mixing it with other tools/certificate sources?

@koakenred
Copy link
Author

Thanks for your quick reaction! I am just using Certify and this function would help us out a lot!

@tvanassche
Copy link

This would also fix a "problem" we were having on our production servers. Certain sites have over 200 bindings, and to make certificate handling easier, we had to split those sites into multiple sites (that redirect to 1 main site).

If Certify would indeed offer the option to filter out hostnames managed by other items, this would make managing those big sites much easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants