The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.

NAME

starman-modcluster - Starman launcher with mod_cluster support

SYNOPSIS

  starman-modcluster --mc-node-name=MyApp1 --mc-uri=http://127.0.0.1:6666 --mc-context="/myapp" --mc-alias="myapp1" --mc-host=127.0.0.1 

OPTIONS

--mc-uri (required)
        --mc-uri http://modclusterserver1.example.com:6666,http://modclusterserver2.example.com:6666
        

mod_cluster address

--mc-node-name (required)
        --mc-node-name UniqueNameOfMyNode

Specified unique name of you server instance, in mod_cluster it is equivalent to JvmRoute. Max site 80 characters

--mc-context (required)
        --mc-context /foo,/bar,/baz/foo
        

Contexts that your application can server.

--mc-host (required)
        --mc-host 10.0.0.5

Specifies the hostname/IP address of a node

--mc-port (optional)
        --mc-port 5000

Specifies the port that application is hosted on, if not specified, will attempt to figure it out.

--mc-type (optional)
        --mc-type http
        

Specifies scheme that is used for your node (http/https), if not specified, will attempt to figure it out.

--mc-alias (optional)
        --mc-alias MyAppServer1,AppServer1
        

Virtual host alias that will be added to httpd. Defaults to StarmanServer

--mc-domain (optional)
        --mc-domain MyGroup
        

Domain/Load balancer name

--mc-status-interval (optional)
        --mc-status-interval 10
        

How often in seconds server is going to communicate its status to mod_cluster. Defaults to 30 seconds.

--mc-multicast-enable
        --mc-multicast-enable 
        

Allow Starman to listen for mod_clusters multicast traffic for dynamic subscription

--mc-multicast-address (optional)

Address to listen multicast traffic on. Defaults to 224.0.1.105

--mc-multicast-port (optional)

Port that mod_cluster is broadcasting its information. Defaults to 23364

--mc-debug (optional)
        --mc-debug 1

Display Net::MCMP debug information, and show configuration options of mod_cluster in the logs.

Other Options

Other options are available as described in starman and plackup

Starman::ModCluster passes through other options given to Starman and Plack::Runner, the common backend that starmna and plackup uses, so the most options explained in plackup -h such as --access-log or --daemonize works fine in starman-modcluster too.

SEE ALSO

starman Starman plackup

1 POD Error

The following errors were encountered while parsing the POD:

Around line 143:

=back without =over