No I'm not talking about a way to update core, I'm talking about my
product which is built on top of cake. I agree with you completely
that this is a bad idea for the cake core. But I think it is something
we could all use for the projects we build that are meant to be used
by more than one client.
I have several clients all whom are at different versions of my
products which is built on a tested specific version of core.
I don't like forcing my clients to update to the newest version on my
schedule, I would rather publish the update is available and let them
update their app when they are ready to do so.

I just think a system like this could be built as a plugin to cake
since every application built on cake has the same problems to solve
when installing/updating. Some of those problems have already been
dealt with very nicely from plugins like Migrations from joelmoss. The
parts that are still missing for me is a clean and simple way to get
the new update to the client without the required need of someone who
knows how to use svn, cvs or git. And then to get it installed into
their existing infrastructure.

Look at the pattern of firefox, eclipse, pear and many other apps
which know how to look for updates for the installed plugins etc. They
periodically check for updates and based on how you've configured the
software either download and update automatically or Ask if you want
to update.

I'm in the middle of breaking my app out into many plugins instead of
one large app, primarily because not every client needs the
functionality of the whole app. And this will allow me to assemble a
new site with the appropriate features for new clients. The plugin
architecture of cake makes it very possible for me to now build custom
plugins for a specific client without bloating the app for everyone
else.

A general rule for me in my development is that "if I do a task more
than once, I should automate that task." I'm finding my updates and
installs are needing to be automated, the problem seems to be the same
problem regardless of the app design eventually you need to install a
new or upgrade an existing.


On Feb 13, 6:34 pm, brian <[email protected]> wrote:
> Are you referring to the Cake core? I don't think that would be a very
> good idea at all. You'd be facing potentially major breakage. That's
> not a swipe at Cake, but you have to understand that some changes will
> possibly require updates to your own code. And, hey, bugs happen.
> Better to test *extensively* before rolling out a new core to
> production. I'd never let one of my clients (that I want to keep) take
> care of that themselves.
>
> And it's really easy to have several core libraries sitting beside
> each other, as you just need to change the path in webroot/index.php
>
> On Fri, Feb 13, 2009 at 3:22 PM, LunarDraco <[email protected]> wrote:
>
> > I have a couple projects that have been deployed to multiple clients/
> > locations.
> > I'm finding it a pain to keep them all updated, so I wanted to make a
> > plugin that would allow me to visit an updates page on the installed
> > site and it would check for updates to the currently installed
> > version.
>
> > I've done some searching and have yet to find anything really useful.
>
> > So my question to the group is first, has anyone already started work
> > on such a service to be used with cakephp apps or plugins?
>
> > Second can the group give me some ideas on requirements that might be
> > useful for such a service.
>
> > I was thinking an updates page which would show the current installed
> > version. A list of possible updates that would be pulled from the
> > service. Weather or not the update requires db Schema changes etc.
> > Possibly a place to specify the URL to look for updates.
>
> > The second part of the update would be the Service App itself that
> > would live on my server where I as a developer can post new releases
> > etc.
>
> > My main goal here is to allow my clients the ability to do a one click
> > update. Which would download the new update, run some scripts on the
> > local server to extract/install the update and then run the db
> > migrations etc.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to