Advanced Deployment

CloudMedic performs many patient, care team and prescription operations out of the box and can be deployed in one-click.  However, if you plan on using it to build your own healthcare application, you are going to have to follow the advanced deployment steps described below.

Start off with your own forked repository:

1. Fork cloudmedic-deploy-public
2. Deploy the template found at '' and use your own forked repo URL in place of the default value given and use your preferred branch

After deploying a forked repo:

1. Fork the AngularJS files from
2. Make custom changes to AngularJS. (If you wish to make changes to the API, those changes can be done directly through the 'cloudmedic-deploy-public' repo you forked.)
3. Make sure you change the deploy.config.js files to point at your desired url

api_url: 'https://{website name}',
base_url: 'https://{website name}',

However, if you are deploying with a personal domain make sure you change '' to your own domain name.

4. Go into your local cloudmedic-angular folder in cmd/terminal and run grunt build:production, and then grunt:compile (If you are starting from a blank state, follow the instructions on Starting from a blank slate)
5. Copy and replace the files in the app folder found in your forked cloudmedic-deploy-public with the bin files from cloudmedic-deploy-public
6. If you have added/removed any files (pictures etc.) make sure you have visual studios reflect those changes.
7. Build the whole cloudmedic-deploy-public project within visual studios
8. Push your changes to your github repository
9. Check the deployment source tab under your app and after it syncs, your app will be deployed.
(if it doesn't appear to be syncing, manually click the sync button)


We have enabled logging on the API using NLog. If you wish to use the built-in logger, add a target in the target section of the NLog.config file to have error logs sent. Information on adding targets can be found at