A Scalable, User-Friendly Source Control System.
Go to file
Adam Simpkins f13e0d9f83 Fix-up commit to resync shipit
Summary:
The previous commit did not update the facebookincubator/fizz-rev.txt
hash (due to running an older version of the shipit code), which is
confusing newer shipit releases that want to keep this file up-to-date.

fbshipit-source-id: 459ae013d33f3f157856320e67a8f6b16ea5e32a
2019-04-29 16:32:15 -07:00
build Fix-up commit to resync shipit 2019-04-29 16:32:15 -07:00
CMake eden: cmake: fixup adding libgit2 options to target 2019-03-29 15:02:04 -07:00
common update copyright headers in some of the common/ stub headers 2019-04-26 14:38:28 -07:00
eden add a copyright header to glibc_en.po 2019-04-26 14:38:27 -07:00
.gitignore eden: wire up mac contbuild 2019-02-05 21:52:30 -08:00
.travis.yml add fbcode_builder sources 2019-04-26 11:31:58 -07:00
CMakeLists.txt eden: cmake: probe for osxfuse headers 2019-03-29 15:02:04 -07:00
CODE_OF_CONDUCT.md Add CODE_OF_CONDUCT.md and reference the LICENSE file in README.md 2019-04-26 14:38:27 -07:00
CONTRIBUTING.md Initial commit 2016-05-12 14:09:13 -07:00
getdeps.py eden: getdeps: skip building rsocket tests 2019-02-19 14:53:22 -08:00
LICENSE Initial commit 2016-05-12 14:09:13 -07:00
make-client.py Isolate low-level overlay logic into FsOverlay 2019-03-11 17:30:21 -07:00
PATENTS Initial commit 2016-05-12 14:09:13 -07:00
README.md Add CODE_OF_CONDUCT.md and reference the LICENSE file in README.md 2019-04-26 14:38:27 -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.

License

See LICENSE.