[Cubicweb] force LDAP source synchronization at startup

Dimitri Papadopoulos Orfanos dimitri.papadopoulos at cea.fr
Sat Oct 18 11:04:11 CEST 2014

Hi Christophe,

Thank you, that's exactly what I was after.

There is even a SynchronizeSourceCommand class in server/serverctl.py
(actually there is such a class for each cubicweb-ctl command). I guess
SynchronizeSourceCommand.run() can be be called from postcreate.py,
can't it?


Le 17/10/2014 21:07, Christophe de Vienne a écrit :
> Hi Dimitri,
> I think you are looking for "cubicweb-ctl source-sync"
> Christophe
> Le 17/10/2014 18:45, Dimitri Papadopoulos Orfanos a écrit :
>> Dear list,
>> We run CubicWeb servers with accounts and groups defined in an LDAP
>> server.
>> For a specific CubicWeb instance, we plan on restoring the database to a
>> previous state quite often. Thus we need to be able to create an
>> instance and reload the database dump rapidly.
>> The script that reloads the database requires some groups to exist.
>> The problem is that account/group sync'ing from LDAP is started long
>> after instantiating and starting an instance. Is there a way of forcing
>> LDAP sync'ing as soon as possible, for example at post-install?
>> Best,
> _______________________________________________
> Cubicweb mailing list
> Cubicweb at lists.cubicweb.org
> http://lists.cubicweb.org/mailman/listinfo/cubicweb

More information about the Cubicweb mailing list