Everlock 0.7.0
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
Documentation
Tag: git
Getting started: Git backend
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 -
Pull requests
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/
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 and over HTTPS, so you clone, fetch, and push with s
Git access control and grants
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
Managing Git repositories
This page covers creating repositories, understanding the naming rules, cloning and pushing over SSH, and the distinction between standalone repositories and the site stores that back Markdown sites.
Versioned storage
Versioned storage is Everlock's internal persistence primitive. Every backend that needs to store state — site content, user records, mail, uploaded files, system configuration — uses it. It is a key-
Getting started
From nothing to a running instance with a published website in ten minutes. First, pick how you want to drive the setup — **the whole guide adapts to your choice**: <style> .surface-tabs { display: fl