Paul Campbell
bf6b4fcd21
All checks were successful
Rust / build (map[name:nightly]) (push) Successful in 7m42s
Rust / build (map[name:stable]) (push) Successful in 10m55s
ci/woodpecker/push/cron-docker-builder Pipeline was successful
ci/woodpecker/push/push-next Pipeline was successful
ci/woodpecker/push/tag-created Pipeline was successful
Release Please / Release-plz (push) Successful in 2m15s
ci/woodpecker/cron/cron-docker-builder Pipeline was successful
ci/woodpecker/cron/push-next Pipeline was successful
ci/woodpecker/cron/tag-created Pipeline was successful
|
||
|---|---|---|
| .. | ||
| actor | ||
| components | ||
| logging.rs | ||
| mod.rs | ||
| README.md | ||
Terminal UI
Currently the Terminal UI is an experimental feature, controlled by the feature flag tui.
Build & Run
The build git-next with the Terminal UI use: cargo install git-next --features tui
To run git-next with the Terminal UI use: git-next server start --ui
Docker
If using the docker image you will need to create a directory to mount that contains the
git-next-server.toml file. Mount this directory as /app. In the example below we use
the current directory for this.
If you want to persist the clones of your monitored repos then point storage.path in
git-next-server.toml to the the directory /app, (e.g. path = "/app/data").
Map the port your webhook notifications are arriving on to the port specified in listen.http.port.
docker run -it -p "8080:8092" -v .:/app/ git.kemitix.net/kemitix/git-next:latest server start --ui
logs
When the Terminal UI is enabled via the --ui parameter, logs are written to the file:
???on Linux~/Library/Application Support/net.kemitix.git-next/git-next.logon MacOS???on Windows
Keys
q- Quitj- Downk- Upf- Page Downb- Page Upg- Top/HomeG- Bottom/End