On Dec 23, 1:50 pm, euromark <dereurom...@googlemail.com> wrote: > http://www.dereuromark.de/2010/08/17/development-vs-productive-setup/
FWIW I used to do the above sort of thing and would say now: bad idea. Why should your test/staging/live site know or have you development db connection data. why should your staging site have your live db connection settings. To use a recent and relevant examlpe: Think about what happend to github recently - through a series of errors the live db got truncated from running a test on a CI server (https://github.com/blog/744-today- s-outage) - that's only possible if the CI server has the access to the live db - which by design you're providing if you provide with the above example. IMO what you're solving in the article is a hack for simply /not/ using the same database.php (and core.php for that matter) file in all environments. Just don't add it to your repo, don't send it if you're ftp/rsyncing files around, setup on first use and the problem of "what evironment should I use" goes away. The technique is certainly useful - but not IMO for the use given. AD Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
