On Tue, 18 Jun 2024 04:58:04 -0500 "David C. Rankin" <drankinatty@xxxxxxxxx> wrote: > On 6/17/24 00:03, Carl Lei wrote: > > What about: create a dedicated "git" user, and run apache as user > > git? After all when new files are to be created they will have > > owner=running program, which could be a CGI program launched from > > apache, or a git program launched from SSH. If these are two > > different users it'll likely become a mess. > > Thank your Carl, that is a thought, but one of last resort. I have > a LOT of things served by Apache, eGroupware, Nextcloud, several > custom authentication frontends to MariaDB and Postgres, and probably > more I'm just not recalling at the moment. Oh, I meant to run another apache instance, serving only the git CGI, and reverse-proxy from your main HTTP server to this dedicated git server. Actually it need not be apache, any kind of server capable of running CGI will do fine.
