Skip to main content

Windows Azure Web Sites: Too easy and too much fun

Microsoft recently landed an incredibly powerful feature: Windows Azure Web Sites. This feature allows developers, designers, and basically anyone to deploy web sites (PHP, NodeJS, Static) to Microsoft's public cloud.

The barrier of entry has been lowered significantly and that's because of the amazing work of the Azure teams. I've attached my slide deck here. In trying to come up with some good slides, I didn't want the audience of 30 people sitting there through a bunch of slides. I wanted it to be more interactive and I wanted to really illuminate how amazingly simple the process is.

In part of the talk, I ended up doing 3 demonstrations


1. Deploying to Azure with Git (git push azure master)

  • created a static html file
  • added azure as a remote
  • pushed to azure within seconds



2. Creating a Wordpress site with a MySQL database

3. Using Express (NodeJS) to deploy a web application to Windows Azure 
  • used the express node module to generate a new site
  • installed all dependencies using npm install
  • changed the listening port to process.env.port so that iisnode can properly manage node (redirecting traffic from IIS and spawning/killing node processes)
  • showed how Azure will automatically detect package.json (and automatically pull down your dependencies)
  • went over a few of the gotchas
    • SSL on shared instances are going to land in the future
    • custom domains only work on reserved instances but this will change in the future


At the end of the talk, I think the audience was really impressed at how easy it was to get going on Windows Azure. Additionally and most importantly, the audience was extremely excited about the actual feature. This was my intention and part of my core principles as being an evangelist for any technology -- Get people excited about the technology so their teams can start adopting it.


Good luck and have fun,
Jaime Bueza

Jaime Bueza is a software engineer in Vancouver, British Columbia, Canada. He has developed web applications for Nintendo, Starbucks, Bacardi, Nike, Electronic Arts, Ritchie Brothers, Kiwi Collections, Cox Communications and Microsoft. When he's not developing useful software that constantly evolves with business requirements, he's writing open source software and helping developers in the Windows Azure NodeJS community.
Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.

Cheers,
Jaime

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:



Now, whenever you make a commit, it should show up like this in the log:



Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this



Want more emojis? check out the Emoji Mardown Cheatsheet!

NodeJS Hack Session: MMO Pokemon with NodeJS/WebSockets

The primary focus of this proof of concept is to determine how easy it is to build real-time web applications for all iPad, iPhone, droids, Safari, Chrome users on top of NodeJS (non-blocking event driven server side Javascript platform). The proof of concept was built within 6-8 hours including the following:

Uses Express framework for server side Javascript development (inspired by Rails / Sinatra / Django)Uses EJS for templating language (much like Django templates and symfony) -- allows partials and passing parameters into partials like symfony PHPReal-time chat using WebSocketsArena Queueing System for real-time competitive matchplay using WebSocketsHTML5 AudioCSS3 transitions for all hand cards, tappable cards, transparent panels, rounded corners, drop shadowsFallbacks for Firefox, IEFirefox/IE will fall back to Flash socketIE will fall back to XHR long poll if the user doesn't have Flash installedNoSQL CouchDB for fetching users and soon cards, achievements, friend associat…