root/greenlock-express.js
2
1
Fork 0
mirror of https://github.com/therootcompany/greenlock-express.js.git synced 2025-11-03 21:42:47 +00:00
Code Issues 43 Releases Wiki Activity

using with pm2 #26

New Issue
Closed
opened 2020-01-13 08:46:51 +00:00 by Ghost · 2 comments
Ghost commented 2020-01-13 08:46:51 +00:00
Copy Link

sorry for asking here
is it possible to use on windows with pm2 cluster mode ?

sorry for asking here is it possible to use on windows with pm2 cluster mode ?
coolaj86 commented 2020-01-13 18:36:42 +00:00
Owner
Copy Link

This is actually the perfect place to ask that.

Short answer

I don't know.

If you turn off clustering in pm2 and turn on clustering in Greenlock Express, that may work.

It will not work with pm2s limited built-in cluster support. You could probably hack it together somehow, but you're probably better off using more standard tools.

Alternatives

You could use something like:

  • nssm or serviceman on Windows
  • systemd on Linux
  • launchctl on macOS

Long Answer

Greenlock Express cannot work in cluster mode with only partial support. It needs to have access to the master process and needs to have direct communication with each worker process.

pm2s built-in clustering spawns worker processes, but since it doesn't know about Greenlock, and Greenlock doesn't know about it, there's no way for the servers to communicate.

I'd be happy to create a custom "Greenlock PM2" module as contract work, but it's not something that I personally use.

This is actually the perfect place to ask that. # Short answer I don't know. If you turn off clustering in pm2 and turn on clustering in Greenlock Express, that may work. It will not work with `pm2`s limited built-in cluster support. You could probably hack it together somehow, but you're probably better off using more standard tools. # Alternatives You could use something like: * `nssm` or [`serviceman`](https://git.rootprojects.org/root/serviceman) on Windows * `systemd` on Linux * `launchctl` on macOS # Long Answer Greenlock Express cannot work in `cluster` mode with only partial support. It needs to have access to the `master` process and needs to have direct communication with each `worker` process. `pm2`s built-in clustering spawns worker processes, but since it doesn't know about Greenlock, and Greenlock doesn't know about it, there's no way for the servers to communicate. I'd be happy to create a custom "Greenlock PM2" module as contract work, but it's not something that I personally use.
coolaj86 commented 2020-01-13 18:57:47 +00:00
Owner
Copy Link

PM2 Docs

Based on what I see here ( https://pm2.keymetrics.io/docs/usage/process-management/#process-configuration ) it seems like you should be able to have it treat Greenlock the same as it would treat an external python or ruby process and run an external version of node rather than doing internal forking.

# PM2 Docs Based on what I see here ( https://pm2.keymetrics.io/docs/usage/process-management/#process-configuration ) it seems like you should be able to have it treat Greenlock the same as it would treat an external `python` or `ruby` process and run an external version of `node` rather than doing internal forking.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
coolaj86
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: root/greenlock-express.js#26
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?