59a7b49781
Summary: The main module of the API server is growing pretty large, since a new method and query parameters struct is required for each new HTTP endpoint added to the server. To make this manageable, let's restructure the code so that each handler function is paired with a params struct that contains its corresponding params. This makes it easier to make changes to individual handlers, such as switching the method GET to a POST and changing the handler to read the params from the request body. Reviewed By: StanislavGlebik Differential Revision: D14222620 fbshipit-source-id: 67abea2ff32a3d6cc278375efd368fa2969ab891 |
||
|---|---|---|
| apiserver | ||
| async-compression | ||
| asyncmemo | ||
| blobimport_lib/src | ||
| blobrepo | ||
| blobrepo_utils | ||
| blobstore | ||
| blobstore-sync-queue | ||
| bonsai-hg-mapping | ||
| bonsai-utils | ||
| bookmarks | ||
| bundle2-resolver | ||
| bytes-ext | ||
| cache-warmup/src | ||
| changesets | ||
| cmdlib/src | ||
| cmds | ||
| common | ||
| failure_ext | ||
| filenodes | ||
| futures-ext | ||
| hgcli | ||
| hgproto | ||
| hook_tailer | ||
| hooks | ||
| mercurial | ||
| mercurial-bundles | ||
| mercurial-types | ||
| metaconfig | ||
| mononoke-api/src | ||
| mononoke-types | ||
| netstring | ||
| phases | ||
| py_tar_utils | ||
| reachabilityindex | ||
| ready_state/src | ||
| repo_client | ||
| revset | ||
| server | ||
| sshrelay | ||
| tests | ||
| .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.