Pivotal is not actively maintaining this release.
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 notifications-service
space.
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
- Add SMTP properties to
./bosh-lite/notifications-smtp-stub.yml
file as follows:
properties:
notifications:
smtp:
host: stmp.example.com
port: 587
user: my-user-name
pass: my-password
- Add DB properties to
./bosh-lite/notifications-db-stub.yml
file for your running MySQL instance as follows:
properties:
notifications:
database:
url: tcp://user:[email protected]:3306/dbname
- Generate manifest:
./bosh-lite/make_manifest
- Create and upload release:
bosh create release
bosh upload release
- Deploy
bosh deploy
bosh run errand deploy-notifications