This is a fork of the sping-music sample application for Cloud Foundry, which extended and adapted to the Multi-Target Application (MTA) model and could be deployed by the CF MTA deploy service.
This is the original spring-music application, which is contained in the root of the project.
This is a Node.js server app that just returns a static JSON with some music news.
This is a Node.js server app that just returns a static JSON with some music news.
TODO
TODO
TODO
TODO
To push the spring-music-news-external app run the following command from the spring-music-news-external directory:
cf push
If the application push fails because of the route already being taken - open the manifest.yml and modify the host entry.
Our MTA has some deployment specific configuration which we should additionally provide in a *.mtaext (MTA extension descriptor) file. In the root folder there are two such files prepared config.mtaext which consumes a database service and a lighter version - config-trial.mtaext which runs with in-memory database and could be deployed on SAP Cloud Foundry Trial without consuming service quota.
Inside the extension descriptor of your choice edit the spring-music-news-external's config url so that it matches your custom host.
Before the change:
url: https://spring-music-news-external-demo.${default-domain}/news
After the change:
url: https://my-custom-hostname.${default-domain}/news
To deploy the MTA archive via CF MTA deploy service run the following command from the root directory:
cf deploy mta-assembly/spring-music.mtar -e config.mtaext
Or if you are deploying the lite version:
cf deploy mta-assembly/spring-music.mtar -e config-trial.mtaext