file_server job from diego/2.92.0
Github source:
bcec567a1
or
master branch
Properties¶
bpm
¶
enabled
¶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
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/
https_listen_addr
¶
Address at which HTTPS server is listening
- Default
0.0.0.0:8443
https_server_enabled
¶
Use HTTPS for serving file_server assets
- Default
false
https_url
¶
The URL provided in file_server link
- Default
https://file-server.service.cf.internal:8443
logging
¶
format
¶
timestamp
¶Format for timestamp in component logs. Valid values are ‘unix-epoch’ and ‘rfc3339’.
- Default
unix-epoch
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
set_kernel_parameters
¶
Enable tuning /proc/sys kernel parameters. NOTE: set this property to ‘false’ when deploying to BOSH-Lite or other containerized BOSH clouds.
- Default
true
tls
¶
cert
¶PEM-encoded tls certificate that can be used for server auth
key
¶PEM-encoded tls key
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/bpm-pre-start
(frombpm-pre-start.erb
)bin/file_server_as_vcap
(fromfile_server_as_vcap.erb
)bin/file_server_ctl
(fromfile_server_ctl.erb
)bin/set-file-server-kernel-params
(fromset-file-server-kernel-params.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/certs/tls.crt
(fromtls.crt.erb
)config/certs/tls.key
(fromtls.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.