Ah, no I think you misunderstood; I meant the version roll-out of the shared app not the cake libs, the app itself would be updated far more frequently then the cake.
As you say, ofcourse, you dont want to give users the ability to make modifications to the app, however, I can think of more then a few use cases in which you would want to expose an api from your app, that allows dev's to interface with some of its internals. If only to allow the flexibility to do things the app developer didnt originally take into account -- since the goal of a design proposed by the OP would be a single shared code-base, he cant take into account the wishes of individual customers. So you probably need to find a way to allow customers to build what they want, by themselves -- even if you don't, compatibility issues will be introduced if all the user can change are his views/templates. You just provide the basic framework. Yet need to devise a way that would allow you to deploy a new feature with minimal impact. Say something like the deployment cycle used on Google App Engine's cloud infrastructure. On Sun, Apr 17, 2011 at 9:12 PM, cricket <[email protected]> wrote: > On Sun, Apr 17, 2011 at 7:37 AM, Yuka Poppe <[email protected]> wrote: >> Hi List, Cricket, >> >> How would version rollout work? With a single codebase, and thus a >> relatively userbase, the project gets big quickly. Customers request >> different features, you'll look at all the feature requests and will >> decide to implement a few that make sense to the whole lot. >> >> There comes a time where you want to introduce these new features a >> few months after your clients have been modifying their site, both the >> templates/views/layout and maybe by extending it with client based >> code or a little custom scripting at certain places (if the webapps >> design allows your clients to do this). You cant just roll out code >> anymore to each and every one of your customers automaticly, at least >> not without allowing your customers to switch and do a test run for a >> few weeks to see if everything still works as it should with your new >> version. >> >> Any ideas about this? Preferably you want them the ability to switch >> back and forth between versions, while working with the live dataset. >> Atleast for a certain period of gracetime, and once this time has >> passed you flip the switch and the bleeding edge version gets forced. >> Or maybe just give them the permanent option of running the bleeding >> edge version, or the previous more stable one? > > Like I said before, one can specify the version to use in webrootindex.php: > > define('CAKE_CORE_INCLUDE_PATH', '/usr/share/php/cake_1.3.7'); > > And the latest stable version gets a symlink (in this case I think a > symlink is the way to go): > > define('CAKE_CORE_INCLUDE_PATH', '/usr/share/php/cake'); > > So users can choose to keep using an older version if they want. > > But ... > >> Ofcourse you could do without all this, especially if there is no way >> for the client to extend or interface with his own code/developers, >> but you would have to make damn sure there are no bugs introduced, or >> you'll have the whole userbase complaining! > > That's for sure. Even allowing the users to set which libs to use is a > bit dicey. It seems to me that this sort of server setup could only > (maybe) work if the users are *not* doing any of their own code > modifications. That would at least make it easier to bump up a > version. > > -- > Our newest site for the community: CakePHP Video Tutorials > http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > [email protected] For more options, visit this group at > http://groups.google.com/group/cake-php > -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
