On Sun, Jul 6, 2008 at 3:26 AM, keymaster <[EMAIL PROTECTED]> wrote:
> Anyways, are you saying you do not put cakephp into SVN as a separare > "vendor", and you don't do vendor branching? How do you handle cake > upgrades? Do just replace the latest cake core folder with each > project and recommit? > This is what I do, you experience may vary. I do not put cake in my own svn. On my server I do an svn export or check out (kind of depends on a couple of factors which I do) of the version of cake that my app is developed to I put this export/checkout into a directory named like /cake_r####/cake <-- where the #### is the cake svn Then I symlink that to the /cake folder on my development and staging servers I use the custom features of the /app/webroot/index.php to detect that it is running in staging/dev and then point the cake core file path to a directory named like above. This way multiple apps targeting multiple cake versions/releases can be supported on the same staging/dev machines. This also makes it very easy to roll back the cake versions on any one of the locations, either by changing the link on the productions boxes or the lines in index.php on the staging/dev machines. After a certain amount of time I will compact and archive the cake_r#### files on the server and no release goes to the server without being 'tagged' with the cake release #### as part of the tag identifier. Hope that makes sense. Now for us a lot of this is automated but you get the idea I would imagine. Sam D --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
