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

Implement a way for ooni-backend to reload the updated TLS certificates #57

Closed
anadahz opened this issue Jun 3, 2016 · 7 comments
Closed

Implement a way for ooni-backend to reload the updated TLS certificates #57

anadahz opened this issue Jun 3, 2016 · 7 comments

Comments

@anadahz
Copy link
Contributor

anadahz commented Jun 3, 2016 •
edited
Loading

This is actually a ticket to overcome the limitation of Github milestones that can include only issues from same repository.
Ref: ooni/backend#90
@anadahz anadahz changed the title Implement a way to for ooni-backend to reload the update TLS certificates Implement a way to for ooni-backend to reload the updated TLS certificates Jun 6, 2016
@anadahz anadahz changed the title Implement a way to for ooni-backend to reload the updated TLS certificates Implement a way for ooni-backend to reload the updated TLS certificates Jun 6, 2016
@anadahz
Copy link
Contributor Author

anadahz commented Jun 14, 2016

This has been implemented here: ooni/backend#91

@anadahz anadahz closed this as completed Jun 14, 2016
@joelanders joelanders reopened this Jun 15, 2016
@joelanders
Copy link
Contributor

joelanders commented Jun 15, 2016 •
edited
Loading

Where is this in #91?

@anadahz
Copy link
Contributor Author

anadahz commented Jun 15, 2016

@joelanders my bad i was confused.

@anadahz
Copy link
Contributor Author

anadahz commented Jun 29, 2016

A workaround is to add pre/post hooks to letsencrypt certificate generation that trigger a docker restart when a new certificate has been generated, relevant code.

@anadahz
Copy link
Contributor Author

anadahz commented Jul 6, 2016

As mentioned in #57 (comment) this is not a blocker for the ooni-backend deployment.

@hellais
Copy link
Member

hellais commented Oct 26, 2016

Is this actually a ooni-sysadmin ticket? It seems like it would actually be more useful as a ooni-backend ticket.

@anadahz
Copy link
Contributor Author

anadahz commented Oct 26, 2016

@hellais indeed it's an ooni-backend issue.

A workaround has been added in the ansible role by using pre/post hooks as described in: #57 (comment)

@anadahz anadahz closed this as completed Oct 26, 2016
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
3 participants
@hellais @joelanders @anadahz