A Scalable, User-Friendly Source Control System.
Go to file
Adam Simpkins 8c00fa3dd7 start splitting up some of the eden doctor code
Summary:
This turns the `doctor.py` module into a package, and starts splitting some of
the code out into different modules.  This should make it easier to maintain
as we continue adding more functionality.

For now I split the base `Problem` classes out into their own module, and I
split the watchman-related checks in their own module.  I will probably
continue splitting additional checks out into their own module.  (I didn't
split them out in this diff just to avoid making the diff too large.)

Reviewed By: strager

Differential Revision: D13372771

fbshipit-source-id: 015dea501ce2898ce7303a419f763f2fc962092f
2018-12-13 19:09:15 -08:00
CMake cmake: compile with -std=gnu++1z 2018-10-23 13:42:12 -07:00
common add FacebookBase2::exportThriftFuncHist() to the fb303 stubs 2018-10-30 13:06:14 -07:00
eden start splitting up some of the eden doctor code 2018-12-13 19:09:15 -08:00
.gitignore ignore the entire external/ directory 2018-04-27 13:05:53 -07:00
CMakeLists.txt cmake: compile with -std=gnu++1z 2018-10-23 13:42:12 -07:00
CONTRIBUTING.md Initial commit 2016-05-12 14:09:13 -07:00
getdeps.py getdeps.py: avoid building rsockets examples and benchmarks 2018-10-26 19:56:29 -07:00
LICENSE Initial commit 2016-05-12 14:09:13 -07:00
PATENTS Initial commit 2016-05-12 14:09:13 -07:00
README.md update README.md 2018-10-30 13:35:40 -07:00

EdenFS is a FUSE virtual filesystem for source control repositories.

EdenFS speeds up operations in large repositories by only populating working directory files on demand, as they are accessed. This makes operations like checkout much faster, in exchange for a small performance hit when first accessing new files. This is quite beneficial in large repositories where developers often only work with a small subset of the repository at a time.

EdenFS has similar performance advantages to using sparse checkouts, but a much better user experience. Unlike with sparse checkouts, EdenFS does not require manually curating the list of files to check out, and users can transparently access any file without needing to update the profile.

EdenFS also keeps track of which files have been modified, allowing very efficient status queries that do not need to scan the working directory. The filesystem monitoring tool Watchman also integrates with EdenFS, allowing it to more efficiently track updates to the filesystem.

Building EdenFS

EdenFS currently only builds on Linux. We have primarily tested building it on Ubuntu 18.04.

TL;DR

[eden]$ ./getdeps.py --system-deps
[eden]$ mkdir _build && cd _build
[eden/_build]$ cmake ..
[eden/_build]$ make

Dependencies

EdenFS depends on several other third-party projects. Some of these are commonly available as part of most Linux distributions, while others need to be downloaded and built from GitHub.

The getdeps.py script can be used to help download and build EdenFS's dependencies.

Operating System Dependencies

Running getdeps.py with --system-deps will make it install third-party dependencies available from your operating system's package management system. Without this argument it assumes you already have correct OS dependencies installed, and it only updates and builds dependencies that must be compiled from source.

GitHub Dependencies

By default getdeps.py will check out third-party dependencies into the eden/external/ directory, then build and install them into eden/external/install/

If repositories for some of the dependencies are already present in eden/external/ getdeps.py does not automatically fetch the latest upstream changes from GitHub. You can explicitly run ./getdeps.py --update if you want it to fetch the latest updates for each dependency and rebuild them from scratch.