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.

Sign up for GitHub

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

Jump to bottom

Command Questions #26

Closed
lazyfrosch opened this issue Mar 31, 2016 · 1 comment
Closed

Command Questions #26

lazyfrosch opened this issue Mar 31, 2016 · 1 comment

Comments

@lazyfrosch
Copy link
Contributor

During implementation yesterday I came up to a few "problems":

  • The cron outputs senseless info every time:
Checking for new version...
Requesting root privileges to run letsencrypt...
   /opt/letsencrypt/.venv/bin/letsencrypt --agree-tos certonly -a webroot --keep-until-expiring --webroot-path /var/www/html -d test.example.com
  • Should we use --no-self-upgrade on cron and certonly?
  • Should we use /opt/letsencrypt/.venv/bin/letsencrypt, and call letsencrypt-auto only once?
@lazyfrosch lazyfrosch mentioned this issue Apr 2, 2016
Merged
@danzilio
Copy link
Member

danzilio commented Apr 4, 2016

@lazyfrosch merged your PR for this. Thanks!

@danzilio danzilio closed this as completed Apr 4, 2016
cegeka-jenkins pushed a commit to cegeka/puppet-letsencrypt that referenced this issue Oct 23, 2017
@lazyfrosch
Split letsencrypt commands, so -auto is only used once
4ba4a54 
So we avoid fiddling with the venv every time, and the cron is now
silent.

refs voxpupuliGH-26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lazyfrosch @danzilio