file_server job from diego/1.35.0
Github source:
6b470cc
or
master branch
Properties¶
bpm
¶
enabled
¶Experimental: use the BOSH Process Manager to manage the file-server process.
- Default
false
diego
¶
file_server
¶
debug_addr
¶address at which to serve debug info
- Default
127.0.0.1:17005
dropsonde_port
¶local metron agent’s port. Deprecated, will be removed when loggregator API v1 support is removed.
- Default
3457
listen_addr
¶Address of interface on which to serve files
- Default
0.0.0.0:8080
log_level
¶Log level
- Default
info
static_directory
¶Fully-qualified path to the doc root for the file server’s static files
- Default
/var/vcap/jobs/file_server/packages/
enable_consul_service_registration
¶
Enable the file-server to register itself as a service with Consul, for client discovery via Consul DNS. Do not disable without arranging alternate service discovery.
- Default
true
loggregator
¶
ca_cert
¶CA certificate to use to verify the metron agent serving the v2 API.
cert
¶Client certificate for the SSH-proxy to use when communicating to the metron agent.
key
¶Private key for the SSH-proxy metron client certificate.
use_v2_api
¶Whether component should use the v2 loggregator API when sending data to the metron agent instead of the ‘legacy’ v1 API.
- Default
false
v2_api_port
¶Port which the component should use to communicate to the metron agent’s v2 API (host is assumed to be
localhost
).
- Default
3458
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/file_server/
directory
(learn more).
bin/file_server_as_vcap
(fromfile_server_as_vcap.erb
)bin/file_server_ctl
(fromfile_server_ctl.erb
)bin/pre-start
(frompre-start.erb
)config/bpm.yml
(frombpm.yml.erb
)config/certs/loggregator/ca.crt
(fromloggregator_ca.crt.erb
)config/certs/loggregator/client.crt
(fromloggregator_client.crt.erb
)config/certs/loggregator/client.key
(fromloggregator_client.key.erb
)config/file_server.json
(fromfile_server.json.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.