So why does TortoiseHg not realize that an existing thgw. When I was doing it on a Windows Server 2000, I didn't want to mess with Apache, and ended up using this HOWTO for setting up hg serve behind nginx: The trick here is that you need to run hg serve as a Windows Service. If I click the start button I get this message in the log as I'd expected:Ībort: cannot start server at ':7999': Only one usage of each socket address (protocol/network address/port) is normally permitted Questions This is incorrect because the port is still listening. If I open that dialog box again via TortoiseHg > WebServer, it reports that the status is "stopped", and the Start button is enabled.
It's ironic that in Task Manager the thgw.exe process is called "TortoiseHg GUI tools for Mercurial SCM" even though there's no GUI running. The web server can be launched from either the Workbench ( Repository Menu) or the Context Menu. Once launched, a computer can connect to the http port and browse your repositories, perform clone, pull, or even push operations if enabled. If I go and run netstat -a -o from a command prompt, I can see that an instance of thgw.exe is running and listening on port 7999 (even after closing the dialog box). From TortoiseHg The serve tool is a wrapper for Mercurial’s built-in web server. Bug:270860 - and executable sections due to nested function usage status:UNCONFIRMED. When I right click on my Hg folder and choose TortoiseHg > Web Server, I can start the web server on port 7999 without a problem.
0 kommentar(er)
