Documentation
Pull requests look simple when a forge is doing the work for you. A contributor creates an account, forks a repository, pushes a branch, and clicks a button. The forge connects all of those pieces and
"Everything is Git" describes the architectural rule behind Everlock. This article is the more mechanical version of that idea. What does it actually mean to build application storage on top of bare G
The 0.9.0 release makes Everlock a git host: repositories are served over HTTP, browsed in a web UI, and built by CI runs that a push starts. It also replaces the two embedded AI models with one that
On most Git forges, a pull request is not really a Git object. It is an application object that happens to point at Git commits. There is usually a database row with an integer id, an author, a state,
Everlock starts with a fairly unreasonable constraint: > Everything that matters should live in Git. Not just the source code for Everlock. The data managed by Everlock. Photos. Calendars. Configurati
The 0.8.0 release adds file shares: a versioned store mounted as a network drive over WebDAV, from Finder, Windows Explorer, a Linux file manager, or `rclone`. Every change is a commit, so a share's h
A repository that collects build artifacts, uploads, or generated data grows forever, and a large file committed once keeps costing disk long after it was deleted. Everlock can bound that: a repositor
The 0.7.0 release tightens who may do what. Access now derives solely from explicit grants, git repositories can hand out a contributor role that opens pull requests without touching branches, and vau
This guide walks through a local first run of Everlock's Git backend: - start Everlock with the SSH frontend and the Git backend - create a user — the bootstrap admin — through the admin SSH console -
Everlock has a built-in pull request system. It is designed around a single principle: a pull request is a ref, not a database record. When you open a pull request, the server creates a Git ref: refs/
Everlock includes a built-in Git service for repositories, site content, and other versioned data. It speaks the normal Git smart protocol over SSH and over HTTPS, so you clone, fetch, and push with s
Everlock uses a path-based grant system to control who can read from and push to repositories. Every access decision — clone, push, admin action — is checked against a table of grants attached to user
