[doc] how and where to set defaults : npx greenlock defaults not working on windows #22

New Issue

Ghost · 2019-12-23T00:12:44Z

Ghost commented

2019-12-23 00:12:44 +00:00

I'm very confused at this point- i read through the available documentation - that is currently very incomplete or miseading
(youtube tutorials with config options that were removed?)

i tried to use the "npx greenlock defaults" command, but when i run it, nothing happens, the process exits after a second without making any changes or providing any useful console.log's or something.

at this point, i am a bit lost and not entirely sure where certain defaults are supposed to be set.

it would be very hepful to have a list of available options e.g:

manager config file
- subscriber email
- tos agreement
- etc i dont really know
req( greenlock-express ).init
- maintainer email
- package root
- package agent
- staging :boolean

i've spent a long time looking through the code, and i think i could set ALL options in .init, but i'm really not sure.

so i'm sorry for this messy issue, but i am really unsure what the best practice is for greenlocks configuration.

I'm very confused at this point- i read through the available documentation - that is currently very incomplete or miseading (youtube tutorials with config options that were removed?) i tried to use the "npx greenlock defaults" command, but when i run it, nothing happens, the process exits after a second without making any changes or providing any useful console.log's or something. at this point, i am a bit lost and not entirely sure where certain defaults are supposed to be set. it would be very hepful to have a list of available options e.g: - manager config file - subscriber email - tos agreement - etc i dont really know - req( greenlock-express ).init - maintainer email - package root - package agent - staging :boolean i've spent a long time looking through the code, and i think i could set ALL options in .init, but i'm really not sure. so i'm sorry for this messy issue, but i am really unsure what the best practice is for greenlocks configuration.

Ghost commented

2019-12-29 13:47:15 +00:00

Is this the same issue as #17?

+1 on being confused about the configuration, but I managed to get the most recent version working using the examples (migrating because I thought renewal was broken and my certs would run out this year). Also I'd like to use wildcard certificates.

For example the readme promises wildcard certs for localhost, but there is missing documentation for it also...

Is this the same issue as [#17](https://git.rootprojects.org/root/greenlock-express.js/issues/17)? +1 on being confused about the configuration, but I managed to get the most recent version working using the examples (migrating because I thought renewal was broken and my certs would run out this year). Also I'd like to use wildcard certificates. For example the readme promises wildcard certs for localhost, but there is missing documentation for it also...

coolaj86 commented

2020-01-10 08:03:48 +00:00

(youtube tutorials with config options that were removed?)

The existing tutorials are for v2, not v3/v4.

I'm going to update the YouTube tutorials, just haven't had the time yet.

readme promises wildcard certs for localhost, but there is missing documentation

Wildcard and localhost certs are supported with DNS-01, which requires integration with a specific DNS provider.

I'm going to base an example around name.com or Digital Ocean, as those are what I use. However, since everyone has a different DNS provider it's not possible to have a generic solution, other than having manual prompts to go set a DNS record and then tell you to hit enter afterwards to continue.

at this point, i am a bit lost and not entirely sure where certain defaults are supposed to be set.

What is it that you're wanting to set? Generally speaking, you don't set anything in init() except for maintainerEmail and configDir.

All domain/site-related configuration is in greenlock.d/config.json for the default file-based config manager. If you want to provide different management callbacks, you put them in a file as specified in the related documentation.

> (youtube tutorials with config options that were removed?) The existing tutorials are for v2, not v3/v4. I'm going to update the YouTube tutorials, just haven't had the time yet. > readme promises wildcard certs for localhost, but there is missing documentation Wildcard and localhost certs are supported with DNS-01, which requires integration with a specific DNS provider. I'm going to base an example around name.com or Digital Ocean, as those are what I use. However, since everyone has a different DNS provider it's not possible to have a generic solution, other than having manual prompts to go set a DNS record and then tell you to hit enter afterwards to continue. > at this point, i am a bit lost and not entirely sure where certain defaults are supposed to be set. What is it that you're wanting to set? Generally speaking, you don't set anything in `init()` except for `maintainerEmail` and `configDir`. All domain/site-related configuration is in `greenlock.d/config.json` for the default file-based config manager. If you want to provide different management callbacks, you put them in a file as specified in the related documentation.

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: root/greenlock-express.js#22