Nibtree in your browser: a Git client with a 3-way merge tool, blame, history and a terminal
342
Nibtree is a Git client with a 3-way merge tool, workspaces, tabs, blame, history and a terminal. This image runs the whole app in your browser, served from a container with git, git-lfs, SSH and GnuPG inside.
docker run --rm -p 4410:4410 \
-v "$PWD:/workspace" \
-v nibtree-home:/home/nibtree \
-e NIBTREE_TOKEN=pick-a-secret \
shibbirweb/nibtree:next
Then open http://localhost:4410/?token=pick-a-secret. Without NIBTREE_TOKEN a new random token is made on each
start, and docker logs shows the address with it.
next: the newest betalatest: the newest stable release (from the first stable release on)0.1.0-beta.13Each tag has linux/amd64 and linux/arm64. The same image is on GitHub as ghcr.io/shibbirweb/nibtree.
/workspace is the folder the app opens. Pass another path inside the container as the command to open
that one instead./home/nibtree holds the settings (~/.nibtree-browser) and git's config. A named volume keeps them
between runs.-v ~/.gitconfig:/home/nibtree/.gitconfig:ro -v ~/.ssh:/home/nibtree/.ssh:ro.--user "$(id -u):$(id -g)", so files the app writes belong to you.-p 9000:4410, also set -e NIBTREE_PUBLIC_URL=http://localhost:9000, so the printed
address is right.compose.yaml runs the same container
with docker compose up -d. It listens on 127.0.0.1 only and restarts with Docker. Put it in the folder you want
to open, then:
NIBTREE_TOKEN=pick-a-secret docker compose up -d
Every page needs the token. Anyone who can reach the port and has the token can read and change the mounted files and run commands in the container, so publish the port only on networks you trust.
npx nibtree@next runs the same app from npmContent type
Image
Digest
sha256:819d422ad…
Size
76.2 MB
Last updated
3 days ago
docker pull shibbirweb/nibtree:next