Yavor Georgiev's Blog

Feb 21

[video]

beat-machine:

3rd place at Startup Weekend Redmond… not bad for a crew of 4

Feb 17

Azure SDK for Node.js 0.5.3 is out

We just pushed out a small February update (0.5.3) to the Azure SDK for Node.js, containing the following fixes:

#81: Start-AzureEmulator errors if there’s a space in the service path: we corrected an issue where the emulator would fail if there was a space in the path to the service
#82: Remove-AzureService prompts for yes/no confirmation: when you want to remove a service, you will now see this prompt to prevent accidental data loss:
```
Confirm
Are you sure you want to remove service "foo"?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help
(default is "Y"):Y
```
#131: Start-AzureEmulator -Launch fails if run twice on the same web role: corrected a problem where our attempt to clean up logs was causing the emulator to crash
#138: Publish-AzureService throws ArgumentNullException when no certificates element provided in .cscfg: this may have affected folks using the Mongo commandlets
#141: Worker role did not allow write access: the user under which Node was running in worker role did not have sufficient permission to write to disk. This may have surfaced as some modules who need to write to disk (such as stylus) failing.

Here is a one-click install of the new bits.

Alongside this, we also released a refresh (0.5.2) of the npm package for Azure, adding support for accessing ServiceBus queues and topics, among other fixes. Read Glenn’s blog post for more details.

Jan 03

One of the most beautiful libraries in the world (Codrington Library at Oxford). UW’s Suzzallo library also made the list.

Dec 13

Node.js/express blog on Azure in 5 minutes

Following up on the announcements and demos shown at today’s Learn Windows Azure event, I decided to put together a very quick demo that gets you going on Azure with a real app as fast as possible.

I decided to modify express’ blog sample to use Azure storage, and also pre-configured all the service/role settings that Azure needs so you can get going as fast as possible.

Here is the 5-minute recipe:

Get your Windows Azure account
Get the Windows Azure SDK for Node.js
Get the sample source code from GitHub. If you are wondering where some of the static content in the sample came from, check out this getting started document.
Get the needed Node packages by running this inside the ExpressBlog\WebRole folder:
```
npm install
```
You should now be able to launch the Windows Azure PowerShell for Node.js shortcut from your start menu. Make sure you run as Administrator. The rest of the steps here should be completed from that shell.
Download your Azure publish settings:
```
Get-AzurePublishSettings
```

Import the settings:

Import-AzurePublishSettings mine.publishsettings

Head to the Azure portal and create a storage account under your subscription. Make note of the account name and access key.
Modify the ExpressBlog\WebRole\Web.cloud.config file where indicated to include the storage settings.
You are now ready to publish. Anywhere inside the ExpressBlog folder, run the following, making sure you use a unique service name:
```
Publish-AzureService -Name uniqueServiceName
```

You’re all done! A Node/Express blog on Azure

Unfortunately things don’t always go according to plan, so in case you get an Internal Server Error or anything else goes wrong after you deploy to the cloud, use this simple trick to debug.

Inside the Web.cloud.config file, enable logging:
```
<iisnode loggingEnabled="true" />
```
Redeploy the service by simply typing:
```
Publish-AzureService
```
Look at the Node.js log file for hints of what may be wrong at http://uniqueServiceName.cloudapp.net/server.js.logs/0.txt