A simple file-based management strategy for Greenlock
Go to file
AJ ONeal bb8056acdc v3.1.1: update docs 2019-11-30 13:42:07 -07:00
tests v3.1.0: update for latest tests (and sites array) 2019-11-30 12:52:33 -07:00
.gitignore v3.1.0: update for latest tests (and sites array) 2019-11-30 12:51:16 -07:00
.prettierrc v0.6.1: bugfixes for greenlock express v3 2019-10-29 05:08:41 +00:00
LICENSE Initial commit 2019-10-21 21:47:37 +00:00
README.md v3.1.1: update docs 2019-11-30 13:42:07 -07:00
manager.js v3.1.0: update for latest tests (and sites array) 2019-11-30 12:51:16 -07:00
package-lock.json v3.1.1: update docs 2019-11-30 13:42:07 -07:00
package.json v3.1.1: update docs 2019-11-30 13:42:07 -07:00

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