Table of Contents

Hardware Requirements

Here are the recommended hardware requirements for running HgLab:

  • Dual-core CPU running at 2 GHz
  • 2 GB of RAM
  • 7200 RPM SAS or, even better, an SSD drive

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).

Notes on Storage Performance

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.

Software Requirements

Note that this is just an overview of what HgLab needs to run. Detailed instructions on how to install each and every bit of software are available here.

Operating System

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.

Internet Information Services

HgLab requires Microsoft Internet Information Services 7.0 or any later version.

Microsoft .NET Framework

On 32-bit systems HgLab requires Microsoft .NET Framework 4.0 and KB2600211.

On 64-bit systems HgLab requires Microsoft .NET Framework 4.5.

Microsoft SQL Server

HgLab requires Microsoft SQL Server 2008 Express or above.

Mercurial

HgLab requires Mercurial 3.6 or above.

Incompatible Software

Having HgLab installed alongside with any of the incompatible software components is not supported.

Microsoft Visual Studio, Microsoft Visual Studio Shell, Development Tools or Debugging Tools

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.

Microsoft Web Deploy Tool

There are certain scenarios when Microsoft Web Deploy Tool could cause problems configuring Internet Information Services (e.g. Microsoft Support Article 2597817).


comments powered by Disqus

Take HgLab for a Spin

Try HgLab now. Full-featured 45-day evaluation, no credit card required.