Last updated on November 8, 2017
Here are the recommended hardware requirements for running HgLab:
The necessary storage space depends on the cumulative size of repositories you want to store in HgLab. Mercurial is very efficient about how it uses storage, but you will want to make sure you plenty of available disk space (10 Gb minimum, likely more).
HgLab is heavily I/O bound, so if you have enough RAM and a powerful CPU, performance will be limited by hard drive seek times. Having a fast HDD (or, better yet, an SSD) will significantly improve responsiveness of HgLab.
HgLab requires Microsoft Windows Server 2008, Microsoft Windows 7 or any later version and supports both 32-bit and 64-bit editions.
Note that support for Microsoft Windows Server 2003 was dropped starting from HgLab 1.5.
There's nothing in HgLab itself that prevents it from running under Microsoft Windows Server 2003. The utter crippleness of MSI and WiX makes it impossible to create a sufficiently reliable installer, thus effectively making it impossible to support Windows Server 2003.
If you want to have HgLab running on Windows Server 2003, please do contact HgLab Support.
HgLab requires Microsoft Internet Information Services 7.0 or any later version.
On 64-bit systems HgLab requires Microsoft .NET Framework 4.5.
HgLab requires Microsoft SQL Server 2008 Express or above.
HgLab requires Mercurial 3.6 or above.
It is generally discouraged to install any version of Microsoft Visual Studio, Microsoft Visual Studio Shell, Development Tools or Debugging Tools of any kind on production servers.
If you happen to have any of those components installed, run the following commands in an Elevated Command Prompt:
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug /v Debugger /f reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework /v DbgManagedDebugger /f reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug /v Debugger /f reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework /v DbgManagedDebugger /f
Remember that editing Registry is a dangerous operation and could cause some components to stop working correctly.
Even with the Registry keys deleted, there could potentially be issues with running HgLab.