blobstore job from bosh/268.7.0
Github source:
3b3fc28
or
master branch
Properties¶
blobstore
¶
agent
¶
additional_users
¶An array of objects with keys ‘user’ and ‘password’ agents must use to access Blobstore via HTTP Basic Auth. These users are in addition to the user defined by ‘blobstore.agent.user’ and ‘blobstore.agent.password’. This is to enable blobstore credential rotation for the agents.
password
¶Password agents must use to access blobstore via HTTP Basic
user
¶Username agents must use to access blobstore via HTTP Basic
allow_http
¶Enable http connections to blobstore, in addition to https
- Default
true
director
¶
password
¶Password director must use to access blobstore via HTTP Basic
user
¶Username director must use to access blobstore via HTTP Basic
ipv6_listen
¶Enable binding to IPv6 addresses
- Default
false
max_upload_size
¶Max allowed file size for upload
- Default
5000m
nginx
¶
enable_metrics_endpoint
¶Expose basic nginx metrics on localhost:/stats endpoint. Uses the ngx_http_stub_status_module (see http://nginx.org/en/docs/http/ngx_http_stub_status_module.html).
- Default
false
workers
¶Number of nginx workers for blobstore
- Default
2
port
¶TCP port blobstore server (ngnix) listens on
- Default
25250
tls
¶
cert
¶
certificate
¶SSL cert for blobstore nginx server
private_key
¶SSL cert key for blobstore nginx server
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/blobstore/
directory
(learn more).
bin/bbr/backup
(frombbr_backup
)bin/bbr/restore
(frombbr_restore
)bin/pre-start
(frompre-start
)config/bpm.yml
(frombpm.yml
)config/mime.types
(frommime.types
)config/nginx.conf
(fromnginx.conf.erb
)config/read_users
(fromread_users.erb
)config/server_tls_cert.pem
(fromserver_tls_cert.pem.erb
)config/server_tls_private_key.pem
(fromserver_tls_private_key.pem.erb
)config/sites/blobstore.conf
(fromblobstore.conf.erb
)config/write_users
(fromwrite_users.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.