| 1 |
# Oxygenhub |
| 2 |
|
| 3 |
A forge for [Oxygen](../oxygen) repositories: hosting, browsing, review, |
| 4 |
issues and releases, in one Rust binary with one data directory. It works |
| 5 |
like GitHub where GitHub is right and differs where Oxygen's commutative |
| 6 |
model makes something better possible. The specification is |
| 7 |
[docs/spec.md](docs/spec.md); deployment notes are in |
| 8 |
[docs/deploy.md](docs/deploy.md). |
| 9 |
|
| 10 |
## Status |
| 11 |
|
| 12 |
Milestones 0.1 (browse), 0.2 (accounts and access), 0.3 (proposals and |
| 13 |
review) and 0.4 (issues and notifications) are done: pages show |
| 14 |
trees, files, blame, history with the dependency graph, changes with diffs, |
| 15 |
comparisons, bookmarks, tags, conflicts, the trust policy and the push log; |
| 16 |
accounts sign in with a password and optional TOTP, create repositories and |
| 17 |
organisations, hold roles, mint scoped tokens for `oxy`, and link their |
| 18 |
Oxygen keys so signed changes are attributed to them; proposals offer a |
| 19 |
bookmark's changes for another with the resulting state, diff and conflicts |
| 20 |
computed before landing, comments anchored to atoms, approvals backed by |
| 21 |
seals, and landing from the hub or from `oxy proposal land`; issues with |
| 22 |
labels, assignees, milestones, cross references and closing keywords; an |
| 23 |
inbox with watching, subscriptions, mentions and optional email; search |
| 24 |
over issues, proposals, repositories and accounts. The API, webhooks and |
| 25 |
checks follow in 0.5. |
| 26 |
|
| 27 |
## Running |
| 28 |
|
| 29 |
``` |
| 30 |
cargo build --release |
| 31 |
target/release/oxygenhub --data /srv/oxygenhub init --base-url https://hub.example:7343 --self-signed |
| 32 |
target/release/oxygenhub --data /srv/oxygenhub admin user create andy --admin |
| 33 |
target/release/oxygenhub --data /srv/oxygenhub serve |
| 34 |
``` |
| 35 |
|
| 36 |
Sign in, create a repository under `+ NEW` and a token under Settings › |
| 37 |
Tokens, then from any checkout: `oxy remote add hub https://hub.example:7343/andy/oxygen`, |
| 38 |
`oxy config remote.hub.token <token>` and `oxy push hub`. With a self-signed certificate, hand clients the CA with |
| 39 |
`OXY_CA=<path>` or `oxy config remote.hub.ca <path>`. |
| 40 |
|
| 41 |
Configuration lives in `<data>/hub.toml` (spec §17.1) and every key can be |
| 42 |
overridden with `OXYHUB_<SECTION>_<KEY>`. |
| 43 |
|
| 44 |
## Layout |
| 45 |
|
| 46 |
``` |
| 47 |
crates/hub the binary: config, db (sqlx + migrations), repos (registry, locks, views), |
| 48 |
protocol (embedded oxy-server), web (pages), api (JSON), render (markdown, |
| 49 |
highlighting, diffs, graph) |
| 50 |
crates/hub-api the JSON API's types, shared with clients |
| 51 |
templates/ askama templates and the stylesheet |
| 52 |
assets/ vendored fonts, icons, the small progressive-enhancement script |
| 53 |
migrations/ under crates/hub; applied at start |
| 54 |
``` |
| 55 |
|
| 56 |
## Developing |
| 57 |
|
| 58 |
`make check` runs formatting, clippy with warnings as errors, and the tests. |
| 59 |
The tests use a real `oxy-core` client against a hub on a loopback port and |
| 60 |
never touch your own Oxygen configuration. |