-
-
Notifications
You must be signed in to change notification settings - Fork 283
Storage Implementations
This page contains a community-contributed list of known Storage implementations for CertMagic.
From the README:
The notion of a "cluster" or "fleet" of instances that may be serving the same site and sharing certificates, etc, is tied to storage. Simply, any instances that use the same storage facilities are considered part of the cluster. So if you deploy 100 instances of CertMagic behind a load balancer, they are all part of the same cluster if they share the same storage configuration. Sharing storage could be mounting a shared folder, or implementing some other distributed storage system such as a database server or KV store.
This table gives the link to each implementation, along with what it uses for its storage mechanism and any requirements for using the implementation.
Name and link | Storage mechanism | Requirements |
---|---|---|
FileStorage (default) |
File system | A folder with read+write permissions |
Caddy-TLSConsul | Consul K/V | Consul |
magicstorage - S3Storage | S3 | AWS |
S3Store | S3 | AWS v2 |
caddy-storage-redis | Redis | Redis |
badgerstorage | Badger | Badger v2 |
DynamoDB | Amazon DynamoDB | AWS |
Generic S3 | S3 (w/ optional client-side encryption using secretbox) | Any S3-alike provider |
Certmagic S3 | S3 Compatible Storage | S3 Compatible Storage |
certmagic-storage-crdb | CockroachDB (SQL) | CockroachDB |
CertMagic SQL Storage | SQL storage | RDB like Postgres |
NATS KV | NATS Key/Value Store | Jetstream enabled Nats cluster/installation |