Hi Sergi,
2017-08-28 12:14 GMT+02:00 Sergi Almacellas Abellana :
> Currently there is a weird behavior if new modules are installed when
> running multiple instances of trytond (as separate process). The problem is
> that only one process has the updated pool definition and the other process
> wi
On 2017-08-28 15:34, Sergi Almacellas Abellana wrote:
> El 28/08/17 a les 15:04, Cédric Krier ha escrit:
> > It is not for me because the problem is in the UI because admin user is
> > not necessary and server administrator. But if the feature is limited to
> > server administrator, there is no pro
El 28/08/17 a les 15:04, Cédric Krier ha escrit:
It is not for me because the problem is in the UI because admin user is
not necessary and server administrator. But if the feature is limited to
server administrator, there is no problem.
When using an orchestration system (like kubernetes), there
On 2017-08-28 14:27, Sergi Almacellas Abellana wrote:
> El 28/08/17 a les 12:46, Cédric Krier ha escrit:
> > On 2017-08-28 12:14, Sergi Almacellas Abellana wrote:
> >> Hi,
> >>
> >> Currently there is a weird behavior if new modules are installed when
> >> running multiple instances of trytond (as
El 28/08/17 a les 12:46, Cédric Krier ha escrit:
On 2017-08-28 12:14, Sergi Almacellas Abellana wrote:
Hi,
Currently there is a weird behavior if new modules are installed when
running multiple instances of trytond (as separate process). The problem
is that only one process has the updated pool
On 2017-08-28 12:14, Sergi Almacellas Abellana wrote:
> Hi,
>
> Currently there is a weird behavior if new modules are installed when
> running multiple instances of trytond (as separate process). The problem
> is that only one process has the updated pool definition and the other
> process wil
