Node.js deployment on Heroku
Please see the attached [login to view URL] for the full project details.
The scope of this project is to implement a good deployment "work-flow" for an existing Node.js app on [login to view URL]
The provided solution should implement (re-use) Node.js / Heroku best practices - [login to view URL]
The "heroku" deployment should work with both http and https
It should be easy to configure a custom domain (i.e. [login to view URL])
Following 3 types of deployment should be allowed
1) One instance of the application deployed to the top level domain root (i.e [login to view URL])
2) Multiple instances of the application mapped / deployed on separate sub-domains ([login to view URL], [login to view URL],
[login to view URL]) - each instance-app could use different environment configuration (different database, different redis, different github repo branch etc).
When deployed like that the deployed applications instance-app1, instance-app2 should be independent of each other and should be independent also (not interfere) with the top level [login to view URL] (which could be a PHP Wordpress site hosted on Godaddy or any other hosting company)
3) Multiple instances of the application mapped / deployed to separate sub-folders ([login to view URL], [login to view URL],
[login to view URL]) - each instance-app could use different environment configuration (different database, different redis, different github repo branch etc).
When deployed like that the deployed applications instance-app1, instance-app2 should be independent of each other and should be independent also (not interfere) with the top level [login to view URL] (which could be a PHP Wordpress site hosted on Godaddy or any other hosting company)
Each above instance-app1, instance-app2, instance-app3, etc. will be linked / mapped to a different github repository branch. Pushing code to the the specific github repository branch will automatically be reflected / deployed on the corresponding (linked) heroku app.
The delivery of this project will be all the required source changes / restructuring required to achieve the requirements along with a very good [login to view URL] file with detailed steps / commands required to implement the above 3 types of different "heroku" deployments. The [login to view URL] file should also describe how to configure https and how to configure / map the custom domain(s) to be used.