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

Let's encrypt task.yml file is present even if I put 'n' as an input when initialization #204

Closed
aniketmaithani opened this issue Dec 10, 2016 · 4 comments

Comments

@aniketmaithani
Copy link
Contributor

I don't know if I got this right or not. But on initial setup of the project even if I put in letsencrypt as n it is still showing the task(s) in the nginx provisioner files? Am I missing something out here??? because in Pydanny's Cookie-Cutter this does not happen?

Hope I am clear.

@saurabh-fueled can you explain this up :)

@theskumar
Copy link
Member

@aniketmaithani the script makes use use of conditional to execute those tasks. When you say not to letsencrypt it essentially sets a variable to not use letsencrypt[1]

[1] https://github.com/Fueled/django-init/blob/master/%7B%7Bcookiecutter.github_repository%7D%7D/provisioner/hosts#L24

@aniketmaithani
Copy link
Contributor Author

Hmmm okay. @theskumar let me check if I can reproduce this issue. I clearly remember I marked use_letsencrypt as n during original scaffolding :) .

@theskumar
Copy link
Member

@aniketmaithani sure, I'm closing this issue for now. Reopen when you face similar issue.

@ShubhamBansal1997
Copy link

Still facing the same issue. Mentioned n while setupping script but getting the fatal: [shubhambansal.me]: FAILED! => {"changed": false, "failed": true, "msg": "Whoops! ssl certificate doesn't exist"} this error

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

No branches or pull requests

3 participants