Re: git dangerous operations on alioth
On 1 March 2013 10:54, Thomas Goirand <firstname.lastname@example.org> wrote:
> On 02/28/2013 06:07 PM, Stefano Zacchiroli wrote:
>> On Thu, Feb 28, 2013 at 10:39:26AM +0100, Daniel Pocock wrote:
>>> Has anybody had experience controlling access to git repositories, for
>>> example, to give users access but prevent some of the following
>>> dangerous operations?
>> Related to this, there is also the risk that a user will ssh on alioth
>> and rm the repository (accidentally or not). Do we have any kind of
>> protection against that? (e.g. backups we can access to without
>> bothering the alioth admins, or a way to give git access but not ssh
>> access, or...)
> Do we have a backup at all? If so, how often is the backup made, and how
> much days of history do we have?
A backup of a git repository is a mirror that constantly does fetch
and never performs garbage collection.
In addition copying across push reflog and even keeping it committed
into git as welll makes sense, this way one can establish when / what
/ how the repository got updated with broken changes.