Generally what I do for production is have all my cake core files out
of my web root path, with each version of cake that I have used in
it's own subfolder then link to a cake_current folder to my production
release dependancy then in index.php in app/webroot/ I have the
following
if (!defined('CAKE_CORE_INCLUDE_PATH')) {
// you can add a switch for your dev environment here as well
define ('CAKE_CORE_INCLUDE_PATH', /full/path/to/cake_current');
}
this way I can quickly upgrade the production site to a new release
and roll back from it and each cake version folder is a svn export of
a specific place in time. I can also tag my source code to tie to a
particular release of cake so my directories might look like
cake_1.2.x_r6336/
cake
cake_1.2.x+r6456/
cake
cake_current -> symlink to cake_1.2.x_r6456
webroot/
app_1
app_2
app_3
then each app can link to the cake version it needs or to to the common _current
Sam D
--
--
(the old fart) the advice is free, the lack of crankiness will cost you
- its a fine line between a real question and an idiot
http://blog.samdevore.com/archives/2007/03/05/when-open-source-bugs-me/
http://blog.samdevore.com/cakephp-pages/my-cake-wont-bake/
http://blog.samdevore.com/cakephp-pages/i-cant-bake/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
