If you want to take a Mercurial repository with you, you have several options:
- Create a server somewhere. Don’t forget to install all the security patches.
- Use an USB stick. Don’t forget it somewhere (like at home) and don’t forget to always push your changes onto it.
- Use Dropbox
Dropbox is a file server in the cloud. While they swear your data is save (“All files stored on Dropbox servers are encrypted (AES-256) and are inaccessible without your account password.” – see the features), it’s better to be safe than sorry. Also, Dropbox can’t really cope with the fast changes to the virtual filesystem done by Mercurial (this will lead to corrupt repositories and missing changesets).
The solution is to create a TrueCrypt container in your Dropbox. Dropbox won’t be able to see any changes as long as the container is mounted. When you dismount the container, Dropbox will check the file for changes (if you write to the container, TrueCrypt just modifies a few sectors). So even if you create a 100MB container, only the initial sync will be slow.
There are few obstacles, though:
- You must remember to mount the container, and push your changes into it.
- If you forget to dismount and push changes into the container on a different computer, you’ll see two containers. In this case, mount the second container somewhere, merge the changes using Mercurial and then commit to the original container.
- You must install TrueCrypt and Dropbox on all computers where you want to use this.
- The cycle “mount-push-dismount” becomes tedious over time.
- If you use HgEclipse, the plug-in will forget the local paths if you forget to mount the container before you start Eclipse.
Why not use bitbucket? They offer free, unlimited private or public hg hosting.
That’s a good solution if your data is not sensitive.