mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 16:57:49 +03:00
db4c509b9e
Summary:
There is a very frustrating operation that happens often when working on the
Mononoke code base:
- You want to add a flag
- You want to consume it in the repo somewhere
Unfortunately, when we need to do this, we end up having to thread this from a
million places and parse it out in every single main() we have.
This is a mess, and it results in every single Mononoke binary starting with
heaps of useless boilerplate:
```
let matches = app.get_matches();
let (caching, logger, mut runtime) = matches.init_mononoke(fb)?;
let config_store = args::init_config_store(fb, &logger, &matches)?;
let mysql_options = args::parse_mysql_options(&matches);
let blobstore_options = args::parse_blobstore_options(&matches)?;
let readonly_storage = args::parse_readonly_storage(&matches);
```
So, this diff updates us to just use MononokeEnvironment directly in
RepoFactory, which means none of that has to happen: we can now add a flag,
parse it into MononokeEnvironment, and get going.
While we're at it, we can also remove blobstore options and all that jazz from
MononokeApiEnvironment since now it's there in the underlying RepoFactory.
Reviewed By: HarveyHunt
Differential Revision: D27767700
fbshipit-source-id: e1e359bf403b4d3d7b36e5f670aa1a7dd4f1d209
|
||
|---|---|---|
| .. | ||
| alpn | ||
| benchmarks | ||
| blobimport_lib | ||
| blobrepo | ||
| blobrepo_utils | ||
| blobstore | ||
| blobstore_sync_queue | ||
| bonsai_git_mapping | ||
| bonsai_globalrev_mapping | ||
| bonsai_hg_mapping | ||
| bonsai_svnrev_mapping | ||
| bookmarks | ||
| bulkops | ||
| cache_warmup | ||
| changesets | ||
| cmdlib | ||
| cmds | ||
| commit_rewriting | ||
| common | ||
| derived_data | ||
| edenapi_server | ||
| edenapi_service | ||
| fastreplay | ||
| filenodes | ||
| filestore | ||
| git | ||
| gotham_ext | ||
| hgcli | ||
| hgproto | ||
| hook_tailer | ||
| hooks | ||
| lfs_import_lib | ||
| lfs_protocol | ||
| lfs_server | ||
| load_limiter | ||
| manifest | ||
| mercurial | ||
| metaconfig | ||
| microwave | ||
| mononoke_api | ||
| mononoke_api_hg | ||
| mononoke_hg_sync_job | ||
| mononoke_types | ||
| mutable_counters | ||
| newfilenodes | ||
| observability | ||
| permission_checker | ||
| phases | ||
| pushrebase | ||
| quiet_stream | ||
| reachabilityindex | ||
| regenerate_hg_filenodes | ||
| repo_attributes | ||
| repo_client | ||
| repo_factory | ||
| repo_import | ||
| revset | ||
| scs_server | ||
| segmented_changelog | ||
| server | ||
| sshrelay | ||
| streaming_clone | ||
| tests | ||
| time_window_counter | ||
| tunables | ||
| unbundle_replay | ||
| walker | ||
| Cargo.toml | ||
| README.md | ||
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.
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