On Wed, Feb 04, 2009 at 08:31:06PM +0100, Andreas Kemnade wrote:
Hi,
On Fri, 30 Jan 2009 17:24:56 +0100 Andreas Kemnade <akemnade@tzi.de> wrote:
Hi Jorge,
On Fri, 30 Jan 2009 12:22:46 -0300 Jorge Arellano Cid <jcid@dillo.org> wrote:
On Fri, Jan 30, 2009 at 01:21:47PM +0000, Jeremy Henty wrote:
Am I the only one getting very poor performance from FreeHG ? Quite often I get a 404 Not Found and right now it's hanging. Everyone confirms that Mercurial itself is really fast and I've seen other reports criticising FreeHG's performance. Perhaps we should think about moving host? It's not always easy to find time to devote to Dillo so it's rather aggravating when that time is wasted just waiting for a connection to the server. I'm committed enough to grit my teeth and wait but I can see it putting off would-be contributors.
Just a thought,
Yes, I've also had trouble with it, and when normal it's slower than our Wearlab's CVS.
A couple of days ago (while developoing/reviewing patches) I digged a bit on it and it seems that bitbucket is much faster. We can try bitbucket while we find a long term solution (e.g. FSF's savannah is offering Mercurial and Git repos, but the applying process may take some time).
At some point in time we should move out from the Wearlab, as it may be closed soon. Currently we need webserver/CGI/python shell accounts and a DCVS (Hg or Git). CGI is quite useful, but we may use another bugtracker too.
The server which actually hosts the dillo debian and openmoko packages should be an alternative. At least performance and bandwidth should be no problem. Maybe moving hg there is a starting point.
ok, try hg clone http://hg.dillo.org/dillo
just add entries for hg.dillo.org in your /etc/hosts to point to that server. 85.214.105.140 hg.dillo.org
It works very well!
push access (with ssl) is not set up yet. When it is done, of course the dns can be changed so that hg.dillo.org points to the right server.
Good. Just let me know when it's done. -- Cheers Jorge.-