Instead of using a local file-based state store, implement a Vault Provider that persists its state to a server such as a SQL back-end (EF?), a NoSQL back-end (DynamoDB, Redis, RavenDB, DocumentDB, etc.) or a remote file store (S3, BLOB, OneDrive, Google Drive, etc).
The Vault Provider interface is fairly simple and won't get too much more complicated, so it's possible to write one or a few base class implementations, and then multiple concrete implementations as per the examples above.
A server-based Vault will make it more manageable to keep track of multiple ACME-issued certs across multiple servers.
Instead of using a local file-based state store, implement a Vault Provider that persists its state to a server such as a SQL back-end (EF?), a NoSQL back-end (DynamoDB, Redis, RavenDB, DocumentDB, etc.) or a remote file store (S3, BLOB, OneDrive, Google Drive, etc).
The Vault Provider interface is fairly simple and won't get too much more complicated, so it's possible to write one or a few base class implementations, and then multiple concrete implementations as per the examples above.
A server-based Vault will make it more manageable to keep track of multiple ACME-issued certs across multiple servers.