route_populator job from cf-app-sd/0.5.0
Github source:
9d0e1cc
or
master branch
Properties¶
app_domain
¶
The domain name for the routes to register.
- Example
-
apps.com
app_name
¶
The name of the app for the route to register.
- Example
-
sample
nats
¶
machines
¶IPs of each NATS cluster member
- Example
|+ - 192.168.50.123 - 192.168.52.123
password
¶Password for NATS authentication
- Example
natSpa55w0rd
port
¶TCP port of NATS servers
- Example
4222
user
¶User name for NATS authentication
- Example
nats
num_routes
¶
Number of routes to populate the routing table with. The routes will be popuated as follows: sample-0.apps.com, sample-1.apps.com, …, sample-100000.apps.com
- Example
-
100000
route_populator
¶
publish_delay
¶The HTTP route populator will emit NATS route registration messages one by one, with this value as the interval between each message. When set to zero, it will send values as fast as possible, but NATS subscribers may lose messages. Be sure to set this to a valid Golang time string.
- Example
50us
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/route_populator/
directory
(learn more).
bin/ctl
(fromctl.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.