Nguyễn Gia Phong <mcsinyx@disroot.org> writes:
As I understand running from git is not secure as it gives gitile
write access to the repos with possibility to corrupt them on error.
I've commented at #71143 about fixing group access for gitile. TLDR:
I agree that documentation update is needed. IMO the following, while
being a breaking change, can make the service more sane and flexible:
1. Allow to change user and group as proposed in the initial patch.
2. Set default user and group to "gitile" and document that if they
changed to other values, they expected to exist on a system, to
avoid warnings like "the following groups appear more than once".
3. Remove the default value of the "repositories" field to enforce
users to specify what they want to serve. Document that gitile's
user/group must have at least read access to this directory.
4. Provide configuration for gitolite as an example, not as default.
5. Remove unnecessary fields like "database" from configuration.
I'm interested what authors and maintainers think about all of this.