Check for new subdomains on restart #1

Open
opened 2020-07-12 12:41:03 +00:00 by Ghost · 0 comments

I've been wasting so much time with this (also because I managed to confuse npx by creating a greenlock.js file in my project). Looking for an easy solution, but confused by the manager documentation what is optional and which is not.

My setup: Deploy via pm2 gitlab pipeline (pm2 sometimes recreates the project folder)
One proxy with greenlock SSL, multiple apps with their own subdomains behind it.

Now, if I add an app, which rarely happens, pm2 just starts a new server if noone is running and restarts the others on demand. So when I restart the proxy, I would expect it to check the configuration and be ready to create new certificates for new subdomains.

Wildcard/DNS challenge is currently not an option.

So how is this done properly with the new config nesting? Tried to implement a manager just with get() and it complains not to have a find method.

How do I inject a new list of altnames on reboot (without logging into the server for npx)?

I've been wasting so much time with this (also because I managed to confuse npx by creating a greenlock.js file in my project). Looking for an easy solution, but confused by the manager documentation what is optional and which is not. My setup: Deploy via pm2 gitlab pipeline (pm2 sometimes recreates the project folder) One proxy with greenlock SSL, multiple apps with their own subdomains behind it. Now, if I add an app, which rarely happens, pm2 just starts a new server if noone is running and restarts the others on demand. So when I restart the proxy, I would expect it to check the configuration and be ready to create new certificates for new subdomains. Wildcard/DNS challenge is currently not an option. So how is this done properly with the new config nesting? Tried to implement a manager just with get() and it complains not to have a find method. How do I inject a new list of altnames on reboot (without logging into the server for npx)?
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 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: coolaj86/greenlock-manager-test.js#1
No description provided.