On 12 May 2012 23:24, Cédric Krier <[email protected]> wrote: > On 12/05/12 22:47 +0100, Craig Barnes wrote: >> a) I am using virtualenv to deploy trytond and all modules + >> dependencies from a working copy, is this acceptable? > > Yes. > >> b) Should I include a database init routine to create the initial >> database with all modules installed? > > It will be good. > >> c) If yes to b) should I add a routine to update all modules in the db? > > Yes, this system must always be up to date. > >> d) The current iteration is a shell script, do I need to convert to >> python for it to be accepted into Tryton-Tools. > > No but try to avoid bashism. >
Once I started looking at these further functions, I decided that Python would be better suited. I pretty much have all functions working with exception to the export, and I have questions regarding the db-init and export. 1) for init-db, I thought it might be desirable to set the translation users, is there a anywhere I can pull this form? 2) Would it be desirable to import the demo data? 3) How should the export work? In place update of po files, or to an archive with the same folder structure? 4) should the I just perform the export for all modules / languages as the only option, or is more fine grained control needed? Thank you -- Craig 'The first time any man's freedom is trodden on - we are all damaged.' Jean-Luc Picard () ascii ribbon campaign - against html mail /\ -- [email protected] mailing list
