dedicated-node job from cf-redis/329
Github source:
b1c7f435
or
master branch
Properties¶
redis
¶
agent
¶
backend_port
¶The backend port for the redis-agent process to listen on
- Default
9876
broker
¶
auth
¶
password
¶The password for HTTP Basic Auth on the agent, also used for the broker
- Default
admin
username
¶The username for HTTP Basic Auth on the agent, also used for the broker
- Default
admin
backend_host
¶The port for the broker unicorn process to run on
backups
¶
access_key_id
¶Access Key ID for the S3-compatible blob store that backups will be uploaded to
- Default
""
bg_save_timeout
¶Timeout in seconds for Redis background save to complete when backing up instance
- Default
3600
bucket_name
¶Name of the bucket into which backups will be uploaded
- Default
""
endpoint_url
¶HTTP(S) endpoint of the S3-compatible blob store that backups will be uploaded to
- Default
""
path
¶Path within the above bucket to which backups will be uploaded
- Default
""
secret_access_key
¶Secret Access Key for the S3-compatible blob store that backups will be uploaded to
- Default
""
dedicated_port
¶The port used by the redis instances
- Default
6379
ssl
¶
key
¶SSL private key for broker (PEM encoded)
pem
¶SSL Certificate for broker (PEM encoded)
start_redis_timeout
¶Maximum wait time in seconds for Redis to start up
- Default
10
config_command
¶The name of the obfuscated redis CONFIG command.
- Default
""
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/dedicated-node/
directory
(learn more).
bin/nginx_ctl
(fromnginx_ctl.erb
)bin/redis-agent_ctl
(fromredis-agent_ctl.erb
)bin/redis_ctl
(fromredis_ctl.erb
)config/agent.yml
(fromagent.yml.erb
)config/backup.yml
(frombackup.yml.erb
)config/nginx.conf
(fromnginx.conf.erb
)config/redis.conf
(fromredis.conf.erb
)config/restore.yml
(fromrestore.yml.erb
)config/ssl/redis-agent.key
(fromredis-agent.key.erb
)config/ssl/redis-agent.pem
(fromredis-agent.pem.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.