Previously, I discussed that I started a side project to discover better ways to build “web apis”. In this case, I am using ASP.NET Web API but I think the lessons I am after could be applied to many technologies and clouds.
One of the things I was looking for was some light continuous deployment after code is committed. At the same time, I wanted to see what the process was to get different kinds of web sites, using different frameworks and technologies, running on Azure Web Sites.
After all, the marketing says it supports .NET, Java, PHP, Node.js, and Python. It also claims continuous deployment. So is it faster, easier to use, and more fun?
What To Deploy?
I created a repository on GitHub called WebJumpStart for the purpose of testing out a few tricks Azure Web Sites has up its sleeve.
In it, you will find three web sites.
- AspNetMvc is an ASP.NET 5 MVC site right out of the gate after File > New Project.
- HelloWorld is just static content files (simple html/js/css files).
- NodeExpress is the Node Express starter site, also unmodified (it is a bit out-of-date at this point, but the magic of npm ensures the versions I’ve picked in package.json are there for me to use).
Note that only one of these projects is based in ASP.NET. HelloWorld and NodeExpress could have been built with notepad, Sublime Text, Brackets whatever…