##// END OF EJS Templates
hg: Redirect Mercurial stdout/stderr to logging when running as WSGI...
hg: Redirect Mercurial stdout/stderr to logging when running as WSGI Any "console" output from Mercurial when Kallithea is running from WSGI should end up in Kallithea's logs. That seems like a nice general feature. This will however also solve another rare but more critical problem: Mercurial is writing to sys.stdout / sys.stderr, using several layers of wrapping. Since Mercurial 5.5 (with https://repo.mercurial-scm.org/hg/rev/8e04607023e5 ), all writes are given a memoryview. Apache httpd mod_wsgi is invoking the WSGI with a custom mod_wsgi.Log injected in sys.stdout / sys.stderr . This logger can however not handle memoryview - https://github.com/GrahamDumpleton/mod_wsgi/issues/863 .

File last commit:

r5433:fbbe80e3 default
r8795:fe050a93 stable
Show More
backup.rst
27 lines | 512 B | text/x-rst | RstLexer

Backing up Kallithea

Settings

Just copy your .ini file, it contains all Kallithea settings.

Whoosh index

The Whoosh index is located in the data/index directory where you installed Kallithea, i.e., the same place where the ini file is located

Database

When using sqlite just copy kallithea.db. Any other database engine requires a manual backup operation.

A database backup will contain all gathered statistics.