A simple file-based management strategy for Greenlock
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
AJ ONeal bb8056acdc v3.1.1: update docs il y a 4 ans
tests v3.1.0: update for latest tests (and sites array) il y a 4 ans
.gitignore v3.1.0: update for latest tests (and sites array) il y a 4 ans
.prettierrc v0.6.1: bugfixes for greenlock express v3 il y a 5 ans
LICENSE Initial commit il y a 5 ans
README.md v3.1.1: update docs il y a 4 ans
manager.js v3.1.0: update for latest tests (and sites array) il y a 4 ans
package-lock.json v3.1.1: update docs il y a 4 ans
package.json v3.1.1: update docs il y a 4 ans

README.md

greenlock-manager-fs.js

A simple file-based management strategy for Greenlock v3

(to manage SSL certificates for sites)

Install

npm install --save greenlock-manager-fs@v3

Usage

npx greenlock init --manager greenlock-manager-fs --config-dir './greenlock.d'

Or, place this file in the root of your project:

.greenlockrc:

{
	"manager": { "module": "@greenlock/manager" },
	"configDir": "./greenlock.d"
}

Example config file

You might start your config file like this:

./greenlock.d/config.json:

{
	"subscriberEmail": "jon@example.com",
	"agreeToTerms": true,
	"sites": [
		{
			"subject": "example.com",
			"altnames": ["example.com", "*.example.com"]
		}
	]
}

CLI Management (coming soon)

We're going to be adding some tools to greenlock so that you can do something like this to manage your sites and SSL certificates:

npx greenlock defaults --subscriber-email jon@example.com --agree-to-terms true
npx greenlock add --subject example.com --altnames example.com,*.example.com
npx greenlock renew --all