@AD the database.php is never included in any rep it is the same for all environments so you can just drag and drop it of COURSE this should be handled differently for ONLINE testing enviroments, i agree
but it doesnt hurt to have the same file for local dev and live stage and the core is the same as well of course. do you have a custom core.php file for each environment? On 23 Dez., 19:56, cricket <[email protected]> wrote: > On Thu, Dec 23, 2010 at 10:40 AM, AD7six <[email protected]> wrote: > > > 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. > > Also, it's worth changing the owner & permissions on these two files > so that you can't accidentally overwrite them with rsync/ftp, but only > directly edit them using sudo in an ssh session. 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
