NPM Compatibility: Adopting Let's Encrypt Standard Directory Structure #4554
viniciuspaes
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
NPM uses a different directory structure from the conventional one.
For example, in a standard setup, the certificates for the domain example.com would be located in the directory:
letsencrypt/live/example.com/...
However, in NPM, the certificates for the domain example.com are stored in the directory:
letsencrypt/live/npm-1/...
This happens because NPM does not use the domain name as the directory name, which can cause compatibility issues with other containers or systems that expect the traditional structure.
Additionally, another inconvenience is that to identify which directory corresponds to a given certificate, it is necessary to check NPM's internal database, making manual administration more difficult.
Is there any specific reason for this choice of structure? Would it be possible to configure NPM to adopt the official standard used by Let's Encrypt?
Beta Was this translation helpful? Give feedback.
All reactions