Deploying with App Manifests
Page last updated:
Warning: Pivotal Application Service (PAS) v2.8 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.
This topic provides basic procedures and guidance for deploying apps with a manifest file.
Manifests provide consistency and reproducibility, and can help you automate deploying apps. Both manifests and command line options allow you to override the default attribute values of
cf push. These attributes include things like number of instances, disk space limit, and memory limit.
cf push follows rules of precedence when setting attribute values:
- Manifests override most recent values, including defaults and values set by commands such as
- Command line options override manifests.
For a full list of attributes you can specify in an app manifest, see App Manifest Attribute Reference.
The following procedure describes how to deploy an app with a minimal manifest. For more information about manifest format and attributes, see App Manifest Attribute Reference.
To deploy an app with a manifest:
manifest.ymlfile in the root directory of your app.
Note: By default, the
cf pushcommand uses the
manifest.ymlfile in the app directory. To specify a different location for the manifest, pass its local path to the
-fflag when you run
Add the following content to the file:
--- applications: - name: YOUR-APP
YOUR-APPis the name of your app.
If you specify any command line options, they override the values specified in the manifest. For more information, see Deploy Multiple Apps with One Manifest.
This section describes how to deploy multiple apps with a minimal manifest. For more information about manifest format and attributes, see App Manifest Attribute Reference.
Follow these general rules when deploying multiple apps with one manifest:
no-routeline in the description of any app that provides background services to another app.
You cannot use any command line options with
cf pushexcept for
- If your manifest is not named
manifest.ymlor not in the current working directory, use the
-fcommand line option.
- If your manifest is not named
To push a single app rather than all of the apps described in the manifest, provide the desired app name by running
cf push YOUR-APP.
To deploy multiple apps with a manifest:
Note: Each app must be in a subdirectory under the same parent directory.
manifest.ymlfile in the directory that contains the apps.
Add each app and its directory to the file. Pivotal Platform pushes the apps in the order specified in the manifest.
Note: If you push multiple apps using a manifest and one fails to deploy, Pivotal Platform does not attempt to push apps specified after the app that failed.
--- applications: - name: APP-ONE path: ./APP-ONE-DIRECTORY - name: APP-TWO path: ./APP-TWO-DIRECTORY
APP-ONEis the name of the first app you want Pivotal Platform to push.
APP-ONE-DIRECTORYis the directory containing the first app.
APP-TWOis the name of the second app you want Pivotal Platform to push.
APP-TWO-DIRECTORYis the directory containing the second app.
From the directory that contains the apps and the manifest, run: