How to set phases.publish = false on a repo or globally on Kallithea?

[Long Vu]

On Sun, Mar 26, 2017 at 6:28 PM, Mads Kiilerich <mads at kiilerich.com> wrote:
> On 03/22/2017 04:31 PM, Long Vu wrote:
>>
>> On Tue, Mar 21, 2017 at 6:34 PM, Sean Farley <sean at farley.io> wrote:
>>>
>>> Long Vu <long.vu at intelerad.com> writes:
>>>
>>>>
>>>> Alternatively, how to set this globally as a default value for all new
>>>> and existing repos?
>
>
> A simple hack is to add it to the "ui" table in the database.
>

Oh nice, I might attempt a local hack just for my usage to get me off
the hook of always have to manually set publish = false for all the
new repos created, which is 90% of the time ... getting tired of it.

Thanks.

> It would be nice (and simple) if this option was exposed in
> Admin/Settings/VCS like for example largefiles are...

Agreed.

>
>> 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?
>
>
> One reason is that the Mercurial config structure also to some extent is
> used when hosting Git repos in Kallithea. It would be weird if Mercurial
> config options kicked in when using Git ... and almost equally weird if they
> only applied to Mercurial repos. That could be solved somehow.
>

Huh, why does Git read Mercurial config?? I don't know Git that much
but I would expect it also have its own config structure under /etc?

> We would also have to figure if it only should use what Mercurial internall
> call "systemrcpath" or also "userrcpath". And to which extent
> `kallithea/lib/utils.py` `make_ui` should reuse logic from
> `mercurial/ui.py`.
>
> /Mads
>



-- 
Long Vu | Build Controller | Intelerad | +1-514-931-6222 ext. 7743

-- 

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.