Fork of patx/hglab.

tokenmess/hglab

The small bottle app the powers this website

$ hg clone https://hglab.io/hg/tokenmess/hglab

HgLab

A small Bottle app that hosts public Mercurial repositories with local user accounts.

Features include public user profiles, repository browsing, commit diffs with comments, README rendering, issues with comments, fork-based pull requests, repository contributors, and HTTP Mercurial clone/pull/push.

Run locally

python3 -m pip install -r requirements.txt
SECRET_KEY=change-me python3 app.py

Then open http://127.0.0.1:8080, create an account, and create a repository.

Python 3.14 requires Mercurial 7.2 or newer. Older Mercurial releases can fail during startup with hgdemandimport/threading.RLock import errors.

Mercurial client use

Clone and pull are public:

hg clone http://127.0.0.1:8080/hg/<user>/<repo>

Push requires the repository owner's or a contributor's username and password:

hg push http://<user>@127.0.0.1:8080/hg/<user>/<repo>

Configuration

  • SECRET_KEY: Bottle signed-cookie secret.
  • HG_HOST_DB: SQLite database path. Defaults to ./data/hghost.sqlite3.
  • HG_HOST_REPO_ROOT: Mercurial repository root. Defaults to ./data/repos.
  • HG_HOST_DEBUG: set to 1 for Bottle debug/reloader.
  • HG_HOST_MAX_FORM_BYTES: maximum browser form POST size. Defaults to 65536.
  • HG_HOST_MAX_RENDER_BYTES: maximum README/file/diff preview size. Defaults to 262144.
  • HG_HOST_MAX_HG_RESPONSE_BYTES: maximum buffered Mercurial HTTP response size. Defaults to 268435456.
  • HG_HOST_RATE_LIMIT_ENABLED: set to 0 to disable in-memory login/signup/hg auth throttling.
  • HG_HOST_RATE_LIMIT_MAX_FAILURES: failed attempts before throttling. Defaults to 5.
  • HG_HOST_RATE_LIMIT_WINDOW_SECONDS: rate limit window. Defaults to 300.
  • HG_HOST_RATE_LIMIT_COOLDOWN_SECONDS: throttle duration. Defaults to 300.
  • PORT: HTTP port. Defaults to 8080.

When HG_HOST_DEBUG is disabled, SECRET_KEY must be set to a non-default value before the app starts.

This v1 stores repositories on local disk. Do not deploy it to ephemeral filesystems unless repository storage is mounted persistently.

SQLite is configured with WAL mode and a busy timeout so a small multi-worker deployment can share one database file. Keep HG_HOST_DB on a local persistent filesystem used by one host; network or synced filesystems can break SQLite locking semantics and should use a server database instead.