Dieter that is something I know, but undoubtedly still need to do. So, the only solution I see (for me) is that I develop some kind of update controller. This controller searches a site, a file, something to get what tasks it needs to do to stay updated. Then performs those updates. Upon completing them it knows this so that it can do it again.
Now, this could happen either initiated by the installed applications or initiated by me on a master application. Of course, I guess a more manual approach would be that I login (since I keep a master login on each of my installations) and run an action controller that looks for my own little "update" file. Now this could be a mere FTP copy and then running a SQL. I could make them depending on what version they are on and which one they are going to. I think it might be better for me via CakePHP because my clients could change their passwords and I would have to find the different password before I could get it updated again. Just thinking out loud on this trying to get some ideas thrown around and see if people agree or disagree with what I am thinking. Basically I want a way for people to pay a monthly fee to stay updated and that I can manage and keep them updated on all the various webservers. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
