On Sunday 02 March 2014 10:24:13 Aymeric Augustin wrote: > On 2 mars 2014, at 08:49, Shai Berger <[email protected]> wrote: > > On Saturday 01 March 2014 19:07:08 Aymeric Augustin wrote: > >> You should never, ever, for any reason, use a different database in > >> development, test and production. It's a bad idea. It doesn't work. > > > > ... except when you're developing for more than one database. Then you're > > allowed to use just one in development > > Fair enough. > > > but you should have CI covering all your targets for testing. Separating > > testing from production really has no excuse, AFAICT. > > I've heard about a web framework that doesn't have CI for all its > targets... ;-)
We tried, and we'll keep trying. And actually, I do run CI for the missing target, it's just not public. But yes, as you said: Fair enough. Shai. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/201403021030.34091.shai%40platonix.com. For more options, visit https://groups.google.com/groups/opt_out.
