Wolfpack is a UNIX like daemon that continously runs in the background. Its purpose is to provide a solid framework for running code when specific events occur in the system, usually triggered by an AMQP message or an incoming webhook.
It wraps the PHP code to ensure any exceptions are handled properly, handles logging and other housekeeping.
Wolfpack is designed to run on many servers and/or instances simultanesouly, be sure to keep this in mind as it does not perform any locking to ensure maximum scalability at all times.
If messages must be processed in a particular order it is up to each individial job to ensure this through it own locking mechanism.
This means each individual instance of Wolfpack is not multi-threaded, but it is multi-processed.
Logging is caught as normal stdin/stdout/stderr.
Wolfpack supports running in multiple copies, and potentially some jobs may take a while to complete. Listener Groups is a way of parallelizing tasks such that you can assign which process handles which particular AMQP queues.
By default the initial wolfpack instance is named the empty string and listens for all events that do not have a specific listener group assigned.
To enable more listener groups, number of instances to enable etc. contact Kodmyran support.
Wolfpack is also used to send commands internal to control the operation of wolfpack itself, such as restarting the daemon in case of new configuration, pausing before and upgrade etc.
These commands are not documented and are not available for extension by third party developers at this time.