On Mar 7, 9:00 pm, "Sonic Baker" <[EMAIL PROTECTED]> wrote:
> On 3/5/07, AD7six <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > On Mar 5, 9:52 pm, "Sonic Baker" <[EMAIL PROTECTED]> wrote:
> > > Hi bakers,
>
> > > I know this has been touched on before but I would like to pay a revisit
> > if
> > > you'll bare with me for a few minutes. With the advent of cakePHP 1.2 on
> > the
> > > horizon people have been coming out with some nice additions to the
> > > framework which require external libraries to be added to the Global
> > > 'Vendors' directory. Since I usually only keep my 'app' directory under
> > > version control this causes me re-think my practices once again.
> > > Therefore, I was wondering if you would take a minute to share your
> > version
> > > control strategies so we may see a show of hands and see the most common
> > > set-ups used.
> > > So, which of the following set-ups do you use:
>
> > > (a) Keep your entire cake installation with your application in your own
> > > Repository and merge new changes as necessary with every new release
> > drop.
>
> > > (b) Keep your entire cake installation with your application in your own
> > > Repository and use svn::externals to point the framework files to the
> > > cakePHP repository.
>
> > That's me too. externals only for the cake folder.
>
> Hi there AD7six,
> Do you mean only the 'cake' subfolder within the framework?
Hi Sonic,
I always use a modified production style install so that everything is
out of the webroot even on shared hosts.
The simple view of what I have is the following:
webroot/
.htaccess
index.php
css/
img/
files/
private_files/
app/
cake/*
vendors/
The cake folder is the only thing that is an external. Everything else
is 'just' in my svn repository.
If you wanted to be 100% covered you could set up your repository as:
Create vendor branch for cake
Copy vendor branch to working copy
remove cake folder contents from working copy
set up cake as external
start coding.
Your upgrade process would typically be:
"update"
The cake folder would be automatically updated to the latest trunk,
unless you specify a specific revision to update to.
Whenever you want, you could updated the vendor cake install code and
any new files/folders that were added by the cake team would be
propogated to your working copy. But it's also usual (or at least good
practice :) ) to EXCLUDE the config folder, so that you don't keep out-
of-syncing your test/live site with your deveopment setup - as such,
and given this is where many of those infrequent changes appear,
managing new folders or file changes outside of the cake folder is
perhaps best as a (rather simple/fast) manual task than a problematic
automated one.
HTH,
AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" 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
-~----------~----~----~----~------~----~------~--~---
