Every now and then we create a module that we want to make sure that behaves differently between production and test environments: prevent from sending e-mails in test, do not send invoices to governmental agencies or send them to their test environment, do not send data to a particular webservice, etc.
In several cases we’ve created a flag on a per use-case basis, we’re considering unifying that into a common flag. It could be named TRYTOND_DATABASE__PRODUCTION or something like that, and its default value would be False.
I was wondering if others would find it useful so that it became a standard flag several modules could rely on.
Yeah, that would be nice, we have also the same problems, we named TRYTOND_SERVER__TYPE and the default string is development and we use production on deployment.
Every action which is configurable can be set differently in config file depending on production/test status, but sometimes it would be better if the code itself could adapt and change its behaviour.
Ultimatly, document formats might be tagged on test service.
Either a flag or a [mode] section in config file would fit.
I would prefer default to be ‘production’ to stay compatible with running versions.
For development I’m using a setup- and start-script (one script, which I use for all projects). This installs trytond, all dependencies from requirements.txt and the module into a virtual environment. One can also define the Tryton version to be used. Then is creates a trytond.conf and a tryton.conf (which eases starting the client), creates a sqlite database and initializes it.
The generated trytond.conf contains configuration for sending mails via sendria. Sendria is like mailcatcher, but implemented in Python, which I prefer. (I even just install it into the virtual environment, which saves me setup effort.) (Thnaks to @timitos for this tip )
)