3 ms·
You could do that, but that means for a shared repo and N git shell accounts you've got N chroots, presumably using null or bind mounts. That's a lot more work
by sigil 10y ago
You could do that, but that means for a shared repo and N git shell accounts you've got N chroots, presumably using null or bind mounts.
That's a lot more work than a restricted shell which just...restricts.
- stephenr 10y agoTrue, it all depends what your requirements are. Personally I'd just designate a path for shared repos (e.g. /srv/vcs/<project>{.git,.hg} etc), give people write access using ACLs and group membership. If they create repos in their home directories, thats their business.