{"id":26221509,"url":"https://github.com/adrianosela/certcache","last_synced_at":"2025-04-17T05:23:13.534Z","repository":{"id":100510641,"uuid":"178783629","full_name":"adrianosela/certcache","owner":"adrianosela","description":"Useful wrappers around the acme/autocert Cache interface","archived":false,"fork":false,"pushed_at":"2024-08-05T15:09:59.000Z","size":69,"stargazers_count":7,"open_issues_count":1,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-03-29T06:01:48.375Z","etag":null,"topics":["autocert","cache","certbot","go","golang","https","server","ssl","ssl-certificates","tls"],"latest_commit_sha":null,"homepage":"","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/adrianosela.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2019-04-01T04:07:30.000Z","updated_at":"2024-08-05T15:09:51.000Z","dependencies_parsed_at":null,"dependency_job_id":"f54a6613-aa6c-4549-a348-9b61a04ea085","html_url":"https://github.com/adrianosela/certcache","commit_stats":null,"previous_names":[],"tags_count":2,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adrianosela%2Fcertcache","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adrianosela%2Fcertcache/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adrianosela%2Fcertcache/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adrianosela%2Fcertcache/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/adrianosela","download_url":"https://codeload.github.com/adrianosela/certcache/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":249318898,"owners_count":21250434,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["autocert","cache","certbot","go","golang","https","server","ssl","ssl-certificates","tls"],"created_at":"2025-03-12T16:20:44.214Z","updated_at":"2025-04-17T05:23:13.516Z","avatar_url":"https://github.com/adrianosela.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"# SSL Certificates Storage\n\n[![Go Report Card](https://goreportcard.com/badge/github.com/adrianosela/certcache)](https://goreportcard.com/report/github.com/adrianosela/certcache)\n[![Documentation](https://godoc.org/github.com/adrianosela/certcache?status.svg)](https://godoc.org/github.com/adrianosela/certcache)\n[![GitHub issues](https://img.shields.io/github/issues/adrianosela/certcache.svg)](https://github.com/adrianosela/certcache/issues)\n[![license](https://img.shields.io/github/license/yangwenmai/how-to-add-badge-in-github-readme.svg)](https://github.com/adrianosela/certcache/blob/master/LICENSE)\n\n### Go tools for managing SSL certificates from acme/autocert\n\nThe [autocert](https://godoc.org/golang.org/x/crypto/acme/autocert) package provides automatic access to certificates from Let's Encrypt and any other ACME-based CA. This repository contains a collection of tools to simplify the task of managing certificates acquired through this method.\n\nWant to have SSL and don't know where to start =\u003e Check out the [sslmgr](https://godoc.org/github.com/adrianosela/sslmgr) package\n\n## Tools:\n* [LayeredCache](https://godoc.org/github.com/adrianosela/certcache#LayeredCache) - chain autocert.Cache implementations\n* [Functional](https://godoc.org/github.com/adrianosela/certcache#Functional) - define an autocert.Cache by using anonymous functions\n\n## Cache Implementations:\n*  [Firestore](https://godoc.org/github.com/adrianosela/certcache#Firestore) - if you are looking for quick and easy\n*  [MongoDB](https://godoc.org/github.com/adrianosela/certcache#MongoDB) - when flexibility and robustness are important\n*  [DynamoDB](https://godoc.org/github.com/adrianosela/certcache#DynamoDB) - if your infra lives in AWS\n*  [S3](https://godoc.org/github.com/adrianosela/certcache#S3) - throw those certs in a bucket\n\n---\n\n#### Why should I use this? Is this for me?\n\nThe [default storage](https://godoc.org/golang.org/x/crypto/acme/autocert#DirCache) mechanism used by autocert is the file system. Containerized and virtual workloads often don't have a persistent file system. Furthermore, file system storage is not suitable for servers spanning multiple machines or distributed systems.\n\nSee that the [autocert.Cache](https://godoc.org/golang.org/x/crypto/acme/autocert#Cache) interface is what controlls where/how certificates are stored/fetched from:\n\n```\nm := autocert.Manager{\n\tPrompt:     autocert.AcceptTOS, // To always accept the terms, the callers can use AcceptTOS\n\tHostPolicy: autocert.HostWhitelist(hostnames...), // Specifies which hostnames the Manager is allowed to respond to\n\tCache:      cache, // Cache is used by Manager to store and retrieve previously obtained certificates and other account data as opaque blobs\n}\n```\n\nI have implemented the [autocert.Cache](https://godoc.org/golang.org/x/crypto/acme/autocert#Cache) interface with popular data stores on major cloud providers; so that **you dont have to!**\n\n#### But wait, why can't I just get a new certificate every time I deploy?\n\nUnless you have a corporate deal with Lets Encrypt, you are [limited](https://letsencrypt.org/docs/rate-limits/) to 5 duplicate certificates (certificates for the same set of names) per week on a rolling basis. This means that if your deployments don't have persistent storage, you can only deploy 5 different times (or even less if your deployments span multiple machines) within a week!\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fadrianosela%2Fcertcache","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fadrianosela%2Fcertcache","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fadrianosela%2Fcertcache/lists"}