blobstore job from cf/251
Github source:
493e5077
or
master branch
Properties¶
blobstore
¶
admin_users
¶List of Username and Password pairs that have admin access to the blobstore. Cloud Controller must use one of these to access the blobstore via HTTP Basic Auth. Example: users: - username: user1 password: password1 - username: user2 password: password2
internal_access_rules
¶List of allow / deny rules for the blobstore internal server. Defaults to RFC 1918 Private Networks. Will be followed by ‘deny all’. See http://nginx.org/en/docs/http/ngx_http_access_module.html for valid rules
- Default
- allow 10.0.0.0/8; - allow 172.16.0.0/12; - allow 192.168.0.0/16;
max_upload_size
¶Max allowed file size for upload
- Default
5000m
nginx_workers_per_core
¶Number of NGINX worker processes per CPU core
- Default
2
port
¶TCP port on which the blobstore server (nginx) listens
- Default
8080
secure_link
¶
secret
¶The secret used for signing URLs
tls
¶
cert
¶The PEM-encoded certificate (optionally as a certificate chain) for serving blobs over TLS/SSL
port
¶The TCP port on which the internal blobstore server listens
- Default
4443
private_key
¶The PEM-encoded private key for signing TLS/SSL traffic
domain
¶
DEPRECATED: The system domain. The public server will listen on host ‘blobstore.system-domain.tld’
system_domain
¶
The system domain. The public server will listen on host ‘blobstore.system-domain.tld’
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/dns_health_check
(fromdns_health_check.erb
)bin/nginx_ctl
(fromnginx_ctl.erb
)bin/pre-start
(frompre-start.sh.erb
)bin/signer_ctl
(fromsigner_ctl.sh.erb
)config/mime.types
(frommime.types
)config/nginx.conf
(fromnginx.conf.erb
)config/sites/blobstore.conf
(fromblobstore.conf.erb
)config/write_users
(fromwrite_users.erb
)ssl/blobstore.crt
(fromblobstore.crt.erb
)ssl/blobstore.key
(fromblobstore.key.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.