HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
alexpeattie
letsencrypt-fromscratch
Ruby2016–2016
alexpeattie / letsencrypt-fromscratch

letsencrypt-fromscratch

A guide to creating a LetsEncrypt client from scratch in < 150 lines of Ruby

Learning & Reference
Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
0Explicit recommenders
113GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A guide to creating a LetsEncrypt client from scratch in < 150 lines of Ruby

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval2 dated mentions

Observed mentions: 2016-03-29 16:38:05 UTC to 2016-04-01 00:47:01 UTC.

012016-03-29 15:00:00 UTC to 2016-03-29 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 29, 15:002016-03-29 18:00:00 UTC to 2016-03-29 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-29 21:00:00 UTC to 2016-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-30 00:00:00 UTC to 2016-03-30 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-30 03:00:00 UTC to 2016-03-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-30 06:00:00 UTC to 2016-03-30 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-30 09:00:00 UTC to 2016-03-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-30 12:00:00 UTC to 2016-03-30 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-30 15:00:00 UTC to 2016-03-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-30 18:00:00 UTC to 2016-03-30 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 30, 18:002016-03-30 21:00:00 UTC to 2016-03-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-31 00:00:00 UTC to 2016-03-31 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-31 03:00:00 UTC to 2016-03-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-31 06:00:00 UTC to 2016-03-31 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-31 09:00:00 UTC to 2016-03-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-31 12:00:00 UTC to 2016-03-31 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-31 15:00:00 UTC to 2016-03-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-31 18:00:00 UTC to 2016-03-31 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-31 21:00:00 UTC to 2016-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-01 00:00:00 UTC to 2016-04-01 03:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 1, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 29, 15:002016-03-29 15:00:00 UTC2016-03-29 18:00:00 UTC110
Mar 29, 18:002016-03-29 18:00:00 UTC2016-03-29 21:00:00 UTC000
Mar 29, 21:002016-03-29 21:00:00 UTC2016-03-30 00:00:00 UTC000
Mar 30, 00:002016-03-30 00:00:00 UTC2016-03-30 03:00:00 UTC000
Mar 30, 03:002016-03-30 03:00:00 UTC2016-03-30 06:00:00 UTC000
Mar 30, 06:002016-03-30 06:00:00 UTC2016-03-30 09:00:00 UTC000
Mar 30, 09:002016-03-30 09:00:00 UTC2016-03-30 12:00:00 UTC000
Mar 30, 12:002016-03-30 12:00:00 UTC2016-03-30 15:00:00 UTC000
Mar 30, 15:002016-03-30 15:00:00 UTC2016-03-30 18:00:00 UTC000
Mar 30, 18:002016-03-30 18:00:00 UTC2016-03-30 21:00:00 UTC000
Mar 30, 21:002016-03-30 21:00:00 UTC2016-03-31 00:00:00 UTC000
Mar 31, 00:002016-03-31 00:00:00 UTC2016-03-31 03:00:00 UTC000
Mar 31, 03:002016-03-31 03:00:00 UTC2016-03-31 06:00:00 UTC000
Mar 31, 06:002016-03-31 06:00:00 UTC2016-03-31 09:00:00 UTC000
Mar 31, 09:002016-03-31 09:00:00 UTC2016-03-31 12:00:00 UTC000
Mar 31, 12:002016-03-31 12:00:00 UTC2016-03-31 15:00:00 UTC000
Mar 31, 15:002016-03-31 15:00:00 UTC2016-03-31 18:00:00 UTC000
Mar 31, 18:002016-03-31 18:00:00 UTC2016-03-31 21:00:00 UTC000
Mar 31, 21:002016-03-31 21:00:00 UTC2016-04-01 00:00:00 UTC000
Apr 1, 00:002016-04-01 00:00:00 UTC2016-04-01 03:00:00 UTC101

What Hacker News says

2 sources
pfg·Apr 1, 2016
Are you referring to the server-side API the client is communicating with, or the internal API the client exposes? The former is documented in the ACME specification[1], currently being worked on by the IETF. There are many low-level ACME libraries for basically every language[2], and a pretty decent guide on writing your own client as well[3]. [1]: https://ietf-wg-acme.github.io/acme/ [2]: https://github.com/letsencrypt/letsencrypt/wiki/Links#librar... [3]: https://github.com/alexpeattie/letsencrypt-fromscratch
In Let's Encrypt and Nginx – State of the art secure web deployment

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.