Our git server is read/write, of course. Authentication is so that only you can push to branches matching u/dimpase/.*, and that is handled by gitolite.
There is no authentication for the cgit repo viewer, as you said. Ideally, everything but the git server and the trac database would be separate (and able to scale horizontally), but thats not the way it is right now. On Tuesday, June 7, 2016 at 12:22:03 PM UTC-4, Dima Pasechnik wrote: > > There is no need to do the git authentication on a trac instance, if its > git server is read-only (and gets updates from another git server, on which > the real pushing is done). > > Here is such a scheme for trac+github integration: > https://github.com/trac-hacks/trac-github > (imho it's a good idea, as it also does a real-time backup of git repo > along the way)... > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
