The Hello All Worlds Demonstration shows how all of the major web development frameworks - PHP, Node.js, and various Microsoft tools from ASP to Razor syntax Web Pages - are all enabled by default in Windows Azure Web Sites.
Clone the repository from the GitHub.com repository.
Open up the Windows Azure Web Sites management portal. Click the New button to start creating a new web site.
Select the Web Site -> Quick Create menu. Then, type in a name for the site. In this example, the site will be named AllInOne.
Click the name of the site (the leftmost column) in the list of sites.
Click the link labeled Set up Git publishing.
Enter in a username and password, then confirm the password, that will be used during the Git deployment process. This is the user account and password you'll use in your Git client.
The portal will reflect the creation of the Git repository has started.
Once the Git repository has been created the portal will reflect the creation has completed.
Click the link labeled Clone Windows Azure site to my computer.
The portal will display a series of commands that, when executed, will result in the Git client cloning the contents of the new site to the client computer.
Copy the command beginning with Git clone... to the clipboard to make execution easier in the next step.
Using the Git Bash command line client, paste (Alt-Space-E-P) in the command copied from the portal.
Note, adding a string at the end of the Git clone command will clone the repository into a separate directory than was copied down from GitHub.com. This wont be required after release, but since the portal is currently not visible to GitHub.com we can't go directly from a GitHub.com repository directly into Windows Azure Web Sites.
The Git repository will be cloned to the client computer and messages will be displayed to the user.
Copy the files from the folder created by cloning the GitHub.com repository into the folder created by cloning the Windows Azure Web Sites repository. Again, this part of the process won't be required following release, we are only doing it to copy the files into the new repository's folder.
Back in the Git Bash client, CD into the new site's repository.
Type the command git add . to add the new files to the site's Git repository
Execute the command git commit -m 'added files for site' in the Git Bash client. This will create a commit to the repository and provide the command you enter as the comment associated with the commit.
The commit message will display in the Git Bash client. Once the process completes, execute the command git push origin master to push the files and the commit message up to the server.
Enter the password used to create the Git repository user.
Note: If you want to see or demonstrate how the portal responds automatically upon a Git commit, make sure the portal window is visible at the same time as this command's execution.
The files will be pushed to the server. As the files are being pushed, Alt-Tab to view the portal browser window or make sure both windows are visible simultaneously.
Each time files are pushed to the server using Git the dashboard will automatically update to reflect the deployment.
Click the deployment item labeled Active Deployment and take note of the menu that appears in the portal.
The menu will appear. Once it does, click the icon labeled Browse.
The Hello All Worlds demo will open up in the browser. Clicking each of the links will open up a different Hello World message in a new browser window.
Click the link labeled Static HTML.
The static file will open in a new browser window.
Clicking each of the additional links will execute each of the Hello World message windows written using each of the frameworks supported by Windows Azure Web Sites. Below, the Node.js sample is visible.
To see the JSON output of the ASP.NET Web API example, press the F12 key to open up the IE developer tools. Click the Network tab, then click the button labeled Start Capturing.
Click the Web API sample link. A dialog may appear requesting the user accept/decline the file-download process. This happens since the output format is JSON, and IE's default behavior is to request the user download JSON files rather than open them up in the browser.
Regardless of the answer provided by the download file-process, the results of the HTTP command are shown as a line item in the browser.
Click the Response body tab to view the JSON output in the tools window.
