Continuing on my previous post on how to set up a Mercurial repository locally in under 5 minutes: what if you now want to push your changes to a remote repository? You might want to collaborate, or maybe you just want the backup. Or you want to develop across multiple machines. This is done very easily too. This is the procedure for Bitbucket, which I use: Fill in the details in the next screen (name, description, private/public repository, etc.). After that,

So you want to make a quick-and-dirty application to test something? And you start and hack away? And it starts looking fairly good? And suddenly it stops working? Here’s a pro-tip: CTRL-Z. For the more down-to-earth devs: use a source control system. I find myself using it more and more, even for mini-projects: from small proof-of-concepts to a static, HTML-only website for a friend. I can strongly advise you to download TortoiseHg and get started. Then, next time you fire

I just go my AppHarbor build to work, and can definitely recommend it if you have a project of your own. It’s a builder server and hosting in one. I switched to Mercurial for this, but it will work with Git also. I just wanted to be able to tell the girls in the club that I use Mercurial. When I push my changes to BitBucket, AppHarbor will pull them in (it also works with GitHub, Codeplex,…), build my solution,