I use a "repository" kind of thingy :-) I have some local sites running on my development machine which are used to create "standard" "components" (components in this case being models/controllers/views which are basically standards for other [production] sites). These are never to be changed on the sites who use them. I use a file in the vendors-directory to set variables that might be needed by the "standard" models/controllers and are specific to the production site.
I keep a self-fabricated suite of tools to synchronize (push) a changed "standard" file to the production server(s), cleaning caches and tmp files etc. as things are being deployed to different OSes, different servers and non-cake applications also, this works remarkably well in my situation. Not very cache-ish though, but it works without too much effort once it is setup. Happy to learn other methods, I can for example think of using svn for such deployment(s). Just my 2ct. Paul > -----Original Message----- > > I build a lot of small web sites and most of them use the same type > of > > controllers so I'd like to be able to have one set of these to update > > instead of 20 to update every time I make a change. Maybe plugins > > would be another route to go, but that would require having to update > > all the sites for every small change I make. > > It has been my experience that CakePHP is not well suited to that > task. If others have done it, I'm sure they will share their > experiences. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
