More process management stuff

[marcj]

Beside the fact that we need to implement more http stuff (but in reactphp/http) we also need to give more tools for production environments like pm2 of the node world it does (https://github.com/Unitech/pm2).

Need is:

1. Monitoring (like pm2 list)
2. Zero downtime deployment
3. Daemonize start command

php-pm's goal should basically be: be in PHP world what pm2 is in the node world.

[kugu]

Anyone working on it?)

[marcj]

I guess no. Willing to contribute? We could need a lot of stuff :)

[kugu]

Yeah, wanted to help. But no time to make it from the begining).

[kugu]

Actualy i'm not realy experienced in process managment.
I don't want study everything from a begining.
So, if someone could explain me basic things. What is the best way. What to read, where to look.
I could figure out and do it)
Main questions:

• What is the best way to demonize php.
• What is the best way to comunicate between processes.
• What is the best way to handle with dead processes.

Best for me means fastest and durable.

[andig]

Check processmanager.php for this implementation.

[bonndan]

What about using a message queue for life cycle management (just an idea)?

• phpreact has some bindings for MQs
• you could use a file watcher that sends "restart" events to the workers in development envs
• workers could listen on "terminate" and handle shutdown themselves (might be more graceful)
• a queue can be used for monitoring, too
• zero downtime possible when workers taken out of round robin (althoug I'd prefer nginx to handle this)
• if the queue is persistent a bit of resilience is added, too

The downside of course is more complexity and another animal in the zoo.

[alexpts]

Also will be great add/delete slave in runtime (scale up/down) via API PM.