Add more complicated access restrictions (repository, branches, tags) about gitblit HOT 18 OPEN

Agreed.  A proof-of-concept blockpush mechanism exists in my master branch.  After the
next release I am going to play with implementing gitosis/gitolite-like functionality
possibly re-using gitosis/gitolite configuration files.

That would be big news !!!! 

Best regards

James,

Do you have any updates on this?

Thanks,

Drew

Not currently.  I keep meaning to find the time to implement something, but so far no
luck.  What needs do you have?  That could help me pin down a spec rather than "remake
gitolite".

Restricting pushes to a branch. For example only a certain user/group can push commits
to a certain branch.

Use case: Everyone can push to master but only the team lead can push to production
after peer review.

You could do this today with the protect-refs.groovy hook script.
https://github.com/gitblit/gitblit/blob/master/groovy/protect-refs.groovy

Thanks James. protect-refs.groovy should be good for now, but I think it'd be nicer
to eventually have this functionality in the UI too.

We have a requirement to allow authenticated read-only access for some users. Specifically,
having some users that are able to log in to the UI (or use a git client) to view the
contents, logs, etc of a specific repo, but not be able to push any changes there.

For the time-being you can use a pre-receive hook to block any pushes.

Hi James,

You wrote:
After the next release I am going to play with implementing gitosis/gitolite-like functionality
possibly re-using gitosis/gitolite configuration files.

It's great! But gitosis' configuration is too poor - use gitolite.
The great example of restrictions configuration is svnserve configuration file. Gitolite's
configuration file format is just as SVN's one - they have required flexibility.

With best regards, Mikhail

access rules
http://sitaramc.github.com/gitolite/rules.html

R, for read only
RW, for push existing ref or create new ref
RW+, for "push -f" or ref deletion allowed (i.e., destroy information)
- (the minus sign), to deny access.

access rules for branches 
http://sitaramc.github.com/gitolite/refex.html

I think that this should be supported right now.

Authenticated Clone & Push non-force (without push -f)

Issue 437 has been merged into this issue.

I see this commit:
"Finer-grained repository access permissions (issue 332)"

It's really nice.
Thank you very much

Thanks.  I'm not quite finished with changes to permissions, but this is definitely
an improvement.

At the moment I have two repos, to mantain the master branch safe.
It would be lot more easier if the gitblit implements some more advanced permisions.

Branch, like in gitolite:
http://gitolite.com/gitolite/rules.html#what-do-rules-look-like
http://gitolite.com/gitolite/refex.html
http://gitolite.com/gitolite/vref.html

This is in yours plans?

I may add something very simple, but I haven't thought about it too much.

More complex ACLs...
1. can be contributed to the core by the community
2. can be written as a Groovy receive hook script
3. can be written as a receive hook plugin

My preference is for someone to attempt #3 - a gitolite-ish receive hook plugin.