Long Vu <[email protected]> schrieb am Mi., 22. März 2017 um 16:31 Uhr:
> On Tue, Mar 21, 2017 at 6:34 PM, Sean Farley <[email protected]> wrote: > > Long Vu <[email protected]> writes: > > > >> Hi, > >> > >> I have 0.3.2. > >> > >> I've been doing this for each new repo creation, when needed, by > >> editing directly the .hg/hgrc of the repo (by going behind Kallithea's > >> back). > >> > >> But I'd like to delegate this to the user creating new repos because > >> we are rolling this out to more and more early adopters/evaluators > >> now. I do not want to be the bottle neck. > >> > >> Alternatively, how to set this globally as a default value for all new > >> and existing repos? > > > > I think the easiest way to do this for Mercurial is to implement what I > > did for Bitbucket by putting the config into the database. Once in the > > database, all Kallithea would need to do is use this extension and set > > an environment variable: > > > > https://bitbucket.org/seanfarley/hgenvconfig > > Alternatively, just throwing an idea here, why Kallithea do not read > the config under /etc/mercurial/hgrc.d/ and other locations in same > order of precedence as the mercurial command line? > > I could have sworn that in the past kallithea DID read the mercurial config file :-/ > Then configuring global mercurial extensions/hooks for the server is > exactly like the command line, no additional work/setup to do. > > I am actually running Kallithea in a Docker so there is no > extensions/hooks config contamination with anything else. > > For people with my use case, this will be the easier option. > > So that's for global configurations. We still Sean solution for per > repo config to be handled by the user I guess. > > > -- > Long Vu | Build Controller | Intelerad | +1-514-931-6222 ext. 7743 > <+1%20514-931-6222> > > -- > > This email or any attachments may contain confidential or legally > privileged information intended for the sole use of the addressees. Any > use, redistribution, disclosure, or reproduction of this information, > except as intended, is prohibited. If you received this email in error, > please notify the sender and remove all copies of the message, including > any attachments. > > _______________________________________________ > kallithea-general mailing list > [email protected] > https://lists.sfconservancy.org/mailman/listinfo/kallithea-general >
_______________________________________________ kallithea-general mailing list [email protected] https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
