&gt; I used to also use append-only storage for changes in potentially buggy or malicious services. Sounds like that might be a good idea, too, to prevent some issues.<p>In a certain sense, git <i>is</i> &quot;append-only&quot;. If you change a commit in history, every ancestor commit will have its SHA hash changed. Naturally this will conflict with other copies of the repository.<p>For backups you should do a &quot;git clone --bare&quot; which checks out the internal git structure with data and history, but not the actual files.