- Azure: My default option since I have the most experience with it and have some monthly credit. However, there is no meteor support in azure websites, so you are stuck either creating your own VM or using ...
- Demeotorizer: a node.js tool that converts a meteor app into a 'standard' node.js app. I saw several blog posts that claimed success with this approach and deploying to multiple providers, but I didn't want to deal with the hassle of building a deploy pipeline that included this.
- DigitalOcean: This is what Rob Connery used in his pluralsight course, but it is the same thing as provisioning your own azure VM with the added disadvantage that there is no 'free' development option and I have no credits for it.
- Galaxy: Meteor's own hosting solution, probably the best in art, but the lack of a developer account made it a bad fit for me. I am all about a 'free' dev/experiment offerings.
- Heroku: My winner. Includes a free dev account, supports git push deployment and can be easily configured to build meteor applications.
This would be my first time using Heroku, how hard can it be?
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.