No description
Find a file
2020-04-22 01:57:57 -05:00
async-git some documentation 2020-04-22 01:57:57 -05:00
async-zlib asdf 2020-04-21 22:40:35 -05:00
docs some documentation 2020-04-22 01:57:57 -05:00
fedhub some documentation 2020-04-22 01:57:57 -05:00
fedhub-hooks some documentation 2020-04-22 01:57:57 -05:00
fedhub-shell updates 2020-04-21 21:32:51 -05:00
.editorconfig todos 2020-04-22 01:43:28 -05:00
.gitignore updates 2020-04-21 21:32:51 -05:00
Cargo.lock restructure 2020-04-22 01:08:08 -05:00
Cargo.toml restructure 2020-04-22 01:08:08 -05:00
config.sample.toml updates 2020-04-21 21:32:51 -05:00
fedhub.sublime-project initial 2020-04-20 00:21:26 -05:00
README.md some documentation 2020-04-22 01:57:57 -05:00

fedhub

Federated git forge.

The software is currently under active development. Expect massive breaking changes.

Setup

You will need a copy of the Rust compiler to build this software. The project layout is fairly standard and running cargo build --all --release should produce the binaries that you need.

fedhub has multiple components. The absolute minimum you need to get started is to create a config file. By default, fedhub looks for config.toml in your current working directory but you can use -c to specify one when running. The config file uses TOML notation and looks a bit like:

addr = "127.0.0.1:3000"
repo_root = "./repos"
redis_url = "redis://127.0.0.1"

For now, you'll need Redis to run this software. I'll look into making a more portable version that uses an in-memory key-value store.

Project Status

Currently, I'm working on website features as well as liberating myself from libgit2 in parallel. libgit2 bindings contain massive amounts of pointer sharing that this application really doesn't need, since all the information I need lives on disk or in cache (in Redis).

Contact

Author: Michael Zhang

License: MIT/Apache-2.0 Dual License