Documentation
Git backend
Everlock includes a built-in Git service for repositories, site content, and other versioned data.
It speaks the normal Git smart protocol over SSH, so you clone, fetch, and push with standard Git clients while Everlock handles storage, auth, and ref updates inside the same system.
What it is for
- serves Git over SSH using the standard smart protocol (clone, fetch, push)
- stores incoming packs as compressed bundle files, preserving delta encoding
- applies ref updates atomically after each push
- enforces access grants per repository and per user
- prunes unreachable objects on demand with
/git repo gc(maintenance) - smart HTTP Git is planned but not yet shipped
How it fits in the system
The Git backend is not isolated. Site stores are pushed through Git — a git push is how content reaches backend-site-http. System configuration is itself versioned. Git is the update path for all human-authored content.
Quick start
Enable the backends, create a repository, clone and push:
/backends enable git-ssh
/git repo create my-project
git clone ssh://admin@localhost:2222/my-project.git cd my-project git add . git commit -m "initial" git push
Sub-pages
- Managing repositories — creating repos, naming rules, the SSH URL format, standalone repos vs site stores
- Pull requests — opening, reviewing, merging, and closing pull requests
- Access control and grants — roles, access paths, granting and revoking access, users and groups