Roundup-demo uses a hard coded url:

 http://localhost:8917/demo/

This is a problem if you are running the server on
a remote linux box that doesn't have a web browser
on it. It would be nice to be able to specify
a server name to use rather than localhost that way
the demo could be explored from a remote system.

-- rouilj

Logged In: YES 
user_id=6405

Patch willingly accepted :) 

Logged In: YES 
user_id=8719

please note that the demo server listens on all network
interfaces.

all you need is stop the demo when demo tracker has been set
up and change the address in demo/config.ini

... perhaps the patch could include just this note?  Richard?

Logged In: YES 
user_id=6405

where? 

Logged In: YES 
user_id=8719

well, in the notice printed on the console when demo starts,
i think.

and maybe in the "for the really impatient" section of
installation.txt too.

Modifying the config.ini as a1s suggests works fine, but is there any reason to prefer a hardcoded 'localhost' over socket.getfqdn()? We're already listening on all interfaces, we might as well be using a useful name. That way the user doesn't have to be bothered with starting the demo, stopping it, reconfiguring it, and then restarting it.

I have a trivial patch ready to make this change if dropping localhost is okay.

yes, there is.

you cannot trust the dns on windows.  until version 0.8 we had problems with unresolvable names returned by gethostname().

people advanced enough to use remote server should be able to reconfigure the tracker if they need to.

I was afraid that Windows would be a problem but when I tried it at work getfqdn() returned what I expected. Granted that's on a moderately well administered Windows domain :-/

I agree it isn't very difficult to modify the config.ini and restart the server. Do you feel that more documentation changes are necessary to make it more "obvious"? If you have suggestions for documentation changes, I can make those.

If it is okay as is, this issue should probably be closed.

yes, i think it would be good to have the case explained in the "For The Really Impatient" section of the installation.txt, and perhaps mentioned in the success_message in the demo.py script.

Hmmm, it appears someone (you :) has actually already added some explanatory text to installation.txt giving some explicit instructions on what to do.

I've essentially cut and pasted them into the success message in demo.py for those who don't read documentation.

Richard seems to have given me CVS access so I've committed that change and am closing this Request. I'm sure someone will let me know if I've done something horribly wrong :)