sapling/edenscm/hgext/infinitepush
Liubov Dmitrieva 1c47c775c0 inifinitepush: add new capability
Summary:
this will be used to understand if server supports 'listkeyspatterns'

(Mononoke doesn't support this)

Reviewed By: DurhamG

Differential Revision: D14107742

fbshipit-source-id: c9a42e8516eb5660ab2f498996b211db7086bcb1
2019-02-18 04:30:32 -08:00
..
__init__.py inifinitepush: add new capability 2019-02-18 04:30:32 -08:00
bundleparts.py codemod: import from the edenscm package 2019-01-29 17:25:32 -08:00
common.py codemod: import from the edenscm package 2019-01-29 17:25:32 -08:00
fileindexapi.py codemod: import from the edenscm package 2019-01-29 17:25:32 -08:00
indexapi.py codemod: move Python packages to edenscm 2019-01-28 18:35:41 -08:00
infinitepushcommands.py codemod: import from the edenscm package 2019-01-29 17:25:32 -08:00
README codemod: move Python packages to edenscm 2019-01-28 18:35:41 -08:00
sqlindexapi.py codemod: import from the edenscm package 2019-01-29 17:25:32 -08:00
store.py codemod: move Python packages to edenscm 2019-01-28 18:35:41 -08:00

## What is it?

This extension adds ability to save certain pushes to a remote blob store
as bundles and to serve commits from remote blob store.
The revisions are stored on disk or in everstore.
The metadata are stored in sql or on disk.

## Config options

infinitepush.branchpattern: pattern to detect a scratchbranch, example
                            're:scratch/.+'

infinitepush.indextype: disk or sql for the metadata
infinitepush.reponame: only relevant for sql metadata backend, reponame to put in
                       sql

infinitepush.indexpath: only relevant for ondisk metadata backend, the path to
                        store the index on disk. If not set will be under .hg
                        in a folder named filebundlestore

infinitepush.storepath: only relevant for ondisk metadata backend, the path to
                        store the bundles. If not set, it will be
                        .hg/filebundlestore