Re: Best Upgrade Path
@leo and @Chris thanks a lot for the input/suggestions. Good call on
the diff on files in app/config/ !
On Jun 18, 10:05 am, leo [EMAIL PROTECTED] wrote:
Maybe it's naïve of me, but I just copy the new cake directory over
the old cake directory (well actually everything but app). I would
expect the app directory to be fairly inviolable by CakePHP. Sure,
there will be times when certain things change like the extension for
template (view) files, but there should be a clear separation between
core and application.
On 18 Juny, 15:15, theandystratton [EMAIL PROTECTED] wrote:
Thanks guys, these are both great and give me some good insight. @Sam
I really like the linking idea, thanks again.
One other question then, does the app directory never need to be
touched? The only thing that confused me was if the configuration
objects/methods have changed, you could be breaking something by
updating your cake directory.
Maybe I'm over-thinking? I think it just makes me nervous introducing
this into a larger environment than shared/virtual hosting for our
apps.
Any thoughts you guys or anyone else on the group can share would be
great!
Thanks,
-Andy
On Jun 6, 1:58 pm, Samuel DeVore [EMAIL PROTECTED] wrote:
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-m...
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Best Upgrade Path
On Wed, Jun 18, 2008 at 9:15 AM, theandystratton [EMAIL PROTECTED] wrote: Thanks guys, these are both great and give me some good insight. @Sam I really like the linking idea, thanks again. One other question then, does the app directory never need to be touched? The only thing that confused me was if the configuration objects/methods have changed, you could be breaking something by updating your cake directory. Sometimes things do change, like the names of options in APP/config/core.php, and I have not found a good way to keep track of those changes. Probably because I'm lazy. Fortunately, Cake does tend to send out quite verbose framework-related error messages and I have on occasion done a simple diff between a stock APP/config/core.php and my current core.php file to see if anything major has changed. Hope that helps. -- Chris Hartjes Internet Loudmouth Motto for 2008: Moving from herding elephants to handling snakes... @TheKeyBoard: http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Best Upgrade Path
Maybe it's naïve of me, but I just copy the new cake directory over
the old cake directory (well actually everything but app). I would
expect the app directory to be fairly inviolable by CakePHP. Sure,
there will be times when certain things change like the extension for
template (view) files, but there should be a clear separation between
core and application.
On 18 Juny, 15:15, theandystratton [EMAIL PROTECTED] wrote:
Thanks guys, these are both great and give me some good insight. @Sam
I really like the linking idea, thanks again.
One other question then, does the app directory never need to be
touched? The only thing that confused me was if the configuration
objects/methods have changed, you could be breaking something by
updating your cake directory.
Maybe I'm over-thinking? I think it just makes me nervous introducing
this into a larger environment than shared/virtual hosting for our
apps.
Any thoughts you guys or anyone else on the group can share would be
great!
Thanks,
-Andy
On Jun 6, 1:58 pm, Samuel DeVore [EMAIL PROTECTED] wrote:
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-m...
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Best Upgrade Path
On Fri, Jun 6, 2008 at 11:52 AM, theandystratton [EMAIL PROTECTED] wrote: We're also thinking about standardizing this for all of our sites eventually, and will definitely want to create a safe, clean, upgrade process as Cake's development continues. The best way I have found to handle this is to have your cake CORE directory in a different place from your cake APP directory, so that way you can update cake CORE without over-writing anything in your Cake APP. Plus, makes it really easy to move code from dev - staging - production if there are slight differences in how each environment is configured. -- Chris Hartjes Internet Loudmouth Motto for 2008: Moving from herding elephants to handling snakes... @TheKeyBoard: http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Best Upgrade Path
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 cake-php@googlegroups.com
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
-~--~~~~--~~--~--~---
