Can't serve multiple repositories anymore using Web Server dialog
Created originally on Bitbucket by janverley (Jan Verley)
We use Tortoise HG inside the company LAN on windows machines.
Very often multiple repositories are served from a single dev machine simultaneously on different ports.
In TortoiseHg version 2.3.1
-
Select repository X in the workbench
-
Select menu "Repository - Web Server ..."
-
a dialog opens and repository X is "hg serve" 'd on port 8000
-
Select repository Y in the workbench
-
Select menu "Repository - Web Server ..." again
-
Dialog opens and repository X is NOT "hg serve" 'd on port 8000 (because the port is in use, visible in the tab Log) The state of buttons clearly indicate this.
-
Choose port 8001 and click Start: repository Y is also "hg serve" 'd, now on port 8001
In TortoiseHg version 4.0
-
Select repository X in the workbench
-
Select menu "Repository - Web Server ..."
-
Dialog opens and repository X is hg serve'd on port 8000
-
Select repository Y in the workbench
-
Select menu "Repository - Web Server ..." again
-
the existing dialog shows again, but nothing is mentioned about repository Y.
Apart from the grey "Local Path" it doesn't differ from the dialog for repository X in the older versions of TortoiseHg. It also shows "Running..." Users easily interpret this as "All is fine, the server is running repository Y"
#Workaround#
- Read the whole dialog
- Stop the server
- Add repository Y to the repositories being served (browsing to it, always defaults to "C:\Windows\System32" for some reason)
- Give the existing repository X also a Path, or else it becomes unreachable ("/")
#In general# I can't find a way to use the UI to start 2 servers, each on their own port.