How do you plan to handle the script (cron_worker_openerp) that handles ir.cron jobs ?
This is tricky, because that script needs a (list of) database names, and we already have use cases where limitation to thoses databases belonging to the system user won't be enough.
Init/update of the database through the recipe is not far behind that one. For the time being, we can live with a simple option to declare the database, even if that's a bit odd (bin/buildout would generate a rc script that can't work until the listed databases have been created).
We had long internal discussions about these issues, with no clear consensus. c2c's input would be appreciated.
How do you plan to handle the script (cron_worker_ openerp) that handles ir.cron jobs ?
This is tricky, because that script needs a (list of) database names, and we already have use cases where limitation to thoses databases belonging to the system user won't be enough.
Init/update of the database through the recipe is not far behind that one. For the time being, we can live with a simple option to declare the database, even if that's a bit odd (bin/buildout would generate a rc script that can't work until the listed databases have been created).
We had long internal discussions about these issues, with no clear consensus. c2c's input would be appreciated.