The Dangerous Convenience of Implicit Ownership
Authorization systems often become complicated one convenience at a time. Everlock ran into a good example of this while working on repository permissions. The original rule sounded harmless:
Documentation
Tag: design
Self-Hosting Passwords Without Trusting the Host
Most self-hosting decisions are decisions about convenience. You move a service onto your own hardware, accept that you are now the person who patches it, and the worst realistic outcome is some downt
Can You Accept a Git Pull Request Without Giving Someone Write Access?
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
Git instead of a database
"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
A merge request is just a ref
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,
Everything is Git
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