3170c13b38
Summary: Mononoke-apiserver now will parse http header in order to get "host" url. Based on that Host url, batch request will return the link to the same host. Requirement: LFS protocol consists of two parts: - "batch" request, GET request - HG client sends ids of the file it wants to download/upload - API server should return valid url for downloading and uploading objects "upload/download" request. - Actual upload/download of the file This diff allows API Server to return the link to itself on "batch" request. So Hg client will go to API Server again for uploading and downloading files. Reviewed By: kulshrax Differential Revision: D12941635 fbshipit-source-id: e56453b0d6239daa3848c285a1df09a4a869f2c8 |
||
---|---|---|
apiserver | ||
async-compression | ||
asyncmemo | ||
blobrepo | ||
blobrepo_utils | ||
blobstore | ||
bonsai-hg-mapping | ||
bonsai-utils | ||
bookmarks | ||
bundle2-resolver | ||
bytes-ext | ||
cache-warmup/src | ||
changesets | ||
cmdlib/src | ||
cmds | ||
common | ||
docs | ||
eden_server | ||
failure_ext | ||
filenodes | ||
futures-ext | ||
hgcli | ||
hgproto | ||
hook_tailer | ||
hooks | ||
hooks_old/src | ||
mercurial | ||
mercurial-bundles | ||
mercurial-types | ||
metaconfig | ||
mononoke-api/src | ||
mononoke-types | ||
netstring/src | ||
py_tar_utils | ||
reachabilityindex/src | ||
ready_state/src | ||
repo_client | ||
revset | ||
server | ||
sshrelay | ||
storage | ||
tests | ||
vfs | ||
.gitignore | ||
.travis.yml | ||
Cargo.toml | ||
CONTRIBUTING.md | ||
LICENSE | ||
packman.yml | ||
README.md | ||
rustfmt.toml |
Mononoke
Mononoke is a next-generation server for the Mercurial source control system, meant to scale up to accepting thousands of commits every hour across millions of files. It is primarily written in the Rust programming language.
Caveat Emptor
Mononoke is still in early stages of development. We are making it available now because we plan to start making references to it from our other open source projects such as Eden.
The version that we provide on GitHub does not build yet.
This is because the code is exported verbatim from an internal repository at Facebook, and not all of the scaffolding from our internal repository can be easily extracted. The key areas where we need to shore things up are:
- Full support for a standard
cargo build
. - Open source replacements for Facebook-internal services (blob store, logging etc).
The current goal is to get Mononoke working on Linux. Other Unix-like OSes may be supported in the future.