This post is part of a series on how we built TwitterMatic.net. Other parts:
First of all, I’m not going into full detail on deployment, as this is really easy: right-click the project in Visual Studio, pick “Publish…”. A package will be built and you will be redirected to the deployment interface, where you can upload the package and start your application. No need to buy servers, no need for your own datacenter: just upload and run!
One more thing though… The default URL’s on which a Windows Azure is hosted, look like http://twittermatic.cloudapp.net. Though this works perfectly, its not a friendly name in my opinion. I want www.twittermatic.net to point to my application!
There’s a reason for providing these unfriendly URL’s though. They are an abstraction to the virtual IP addresses that Windows Azure uses, making it easier to changes these IP’s without having to stop or disrupt your application.
If you want to make use of your own domain name, there’s an easy option: create a CNAME record in your DNS, and you’re done. For TwitterMatic, I’ve created the following records in my nameserver:
www.twittermatic.net IN CNAME twittermatic.cloudapp.net
Ask your ISP to fix this for you, or check Steve marx’ blog post on how to do this with GoDaddy.com.
“Everything seemed to fall in place. A moment of peace was about to fall on the digital village, since the digital villagers could now tell the latest stories, even when they were asleep or busy working. Knight Maarten The Brave Coffeedrinker finished his job. A sample application in the cloud was created. It was time for him to move on to a new quest.”
If you want the source code for TwitterMatic, check http://twittermatic.codeplex.com.
This is an imported post. It was imported from my old blog using an automated tool and may contain formatting errors and/or broken images.