This release deploys the notification service as an application onto the CloudFoundry platform.
A running CF is required to deploy.
The application will be deployed into the
system org, and the
The service registers itself at the address matching http://notifications.$CF_APP_DOMAIN.
- Running UAA. This requirement is typically satisfied by having CloudFoundry deployed.
- Running MySQL instance. One option is to deploy the CloudFoundry MySQL release.
Notifications requires a UAA client to boot. The client can be created with the following properties:
scope: uaa.none client_id: notifications authorized_grant_types: client_credentials authorities: scim.read,cloud_controller.admin
- Use the latest notifications final release available, it generally contains bug-fixes.
- Do not cut a release yourself unless you are very familiar wth bosh.
- Add SMTP properties to
./bosh-lite/notifications-smtp-stub.ymlfile as follows:
properties: notifications: smtp: host: stmp.example.com port: 587 user: my-user-name pass: my-password auth_mechanism: plain
- Add DB properties to
./bosh-lite/notifications-db-stub.ymlfile for your running MySQL instance as follows:
properties: notifications: database: url: tcp://user:email@example.com:3306/dbname
- Generate manifest:
- Update the sub-modules of the release
- Upload latest final release from the /releases dir:
bosh upload release releases/notifications/notifications-X.yml
bosh deploy bosh run errand deploy-notifications
In addition to the stub file properties specified in the BOSH-Lite manifest, an AWS manifest stub file will require some extra infrastructure specific fields. Included below is an example:
infrastructure_properties: availability_zone: us-east-1a