Took a while to track this down so wanted to capture it and maybe useful for others if trying to use nuget with mono on linux
I’m lucky enough to have Myles work on my team and earlier this year he put together a nice intro into TDD which is well worth reading.
Nice presentation on how the guys at Github built out the next version of GitHub pages using Basho’s Riak KV store and webmachine (which is an Erlang web framework )
The future!
We’ve launched a series of short videos showing some of the key use cases of sharpcloud to help solve key business problems such as:
Don’t forget you can sign up and try sharpcloud for yourself here
Interesting presentation on DropBox “security/privacy/TOS issues” and how you can operate you’re own version utilising open source code - something I intend to look at. The software can be found here: http://lipsync.it/
“A higher probability exists that every member of your programming team will be attacked and killed by wolves in unrelated incidents on the same night.” - Great dive under the hood of Git
So node.js is hot and it’s been something I’ve been playing with for a while now in a purely kick the tyres type way. Now sharpcloud lives in a Windows Azure world and while we’ve been busy utilising amazing tools like Redis and MongoDB in our Azure production environment Node.js has been something that we’ve not been able to utilise as realistically it needed a native port to make use of IO completion ports to get the full node.js async goodness.
So back in May Ryan Dahl (the creator of node.js) presented the future of node.js and in it was a view to bringing a native version of node.js onto windows. Obviously this was exciting news but it was unclear what the timeframe would be so I withheld too much joy :-) …then I saw this post indicating Microsoft were aiding in the effort which increased my excitement (geeky I know).
Jump forward a few weeks and low and behold an unstable v.0.5 release is available as a native windows binary - fantastic stuff. Anyway my attention immediately turned to trying and getting a test deployment on Windows Azure and that’s exactly what I’ve done.
I’ve created a skeleton Azure VS2010 solution with a worker role that houses node.js and binds it to port 80, and I’ve succesfully run it on the Azure cloud which can be seen here (note: this may disappear at some point). I’ve also pushed the solution to my GitHub account here so feel free to use it to starting taking advantage of Node.js goodness on Windows Azure.
