PCF Manifest file - reference

Manifest file is a way by which you can configure a pcf application without having to use much CLI commands every time you deploy an application. 

A sample manifest file for reference. The application name is mandatory. 

--applications: 

• Name: myappname <name of the application>

Memory: 512M <Mmemory to allocate for this app M, MB, G, GB (upper or lower case)

Instances: 2 <no. Of instances> 

Buildpack: https://github.com/cloudfoundry/java-buildpack.git <buildpack url or local build pack name>

path: /dist/myapp.jar <location of your application artifact>

host: my-application

(or)

hosts: 

- my-application-1

- my application-2

(or)

no-hostname: true

Command: bundle exec rake VERBOSE=true <command to be executed during startup>

disk_quota: 1024M <disk quota to allocate> 

docker: 

image: dockerimage-repo/imagename <docker image name>

username: docker-user-name <user-name for the docker>

domain: abc.com <domain name>

(or)

domains:

- abc1.com

- abc2.com

random-route: true <do you want to use a random route to be generated dynamically>

(or)

routes:

- route: test1.abc.com

- route: test2.abc.com

(or)

route-path: test.abc.com

(or)

no-route: true <do you want the app to not have any route> 

stack: cflinuxfs2 <stack to be used>

timeout: 60 <timeout in seconds for starting the application> 

services: 

- mysql-db <name of the service to be bound>

- dvn-new-relic <name of the service to be bound>

env: <environment variables to be used >

APP_HEADER_NAME=Deivee APP

LOCATION=TEXAS

health-check-type: http <http | port | process>

health-check-http-endpoint: /performHealthcheck <custom url for CF to check health of app>