I have a client’s Django project that I’m developing locally, using Mercurial for version control. I push my local repository to my personal remote server (where I keep all my projects) and then when I come to deploy it (on whichever web server) I clone that respository there from my personal server.
This works fine on most servers (where I have total control) but I have a few projects where I’m deploying on to WebFaction. WebFaction is great, but a little unusual with it’s setup, as I need to first declare the Django project as an ‘application’ through their control panel. This creates a few things automatically, such as an ‘apache2’, ‘myproject’, etc folder. It’s this same folder though where I want to clone the repository from my personal remote server. Doing the usual hg clone command just doesn’t work though as it says the destination folder already exists. There isn’t much I can do about the contents of this folder really, so I need to work around this.
I’m not an expert at Mercurial and the only way I could seem to work it out is clone it to another folder and then moving all the contents (including the .hg) into the actual folder I want. This seems silly though…
I’m using Mercurial v1.6.2 (installed through easy_install). Could anyone share some light on this?
Many thanks.
In the main, it looks like you might be trying to use Mercurial as an installation manager which is certainly not its design goal.
If I am reading you correctly, part of your source repository should be something like
make deploywhich puts the files into their proper places. Put another way, having a repository clone (in.hg) in your deployment directory seems odd and trouble-prone.