| Update System - Best practice |
[eluser]Phil Sturgeon[/eluser]
SVN is fine if you have control over all the servers your app will be installed on. I personally use Git and do the same thing. However I am looking to set up a more portable method as not everyone will be using Git to manage their PyroCMS updates. I think, a REST service offering a list of modules with version numbers and other meta data, combined with a local XML or JSON file within the module could be used to compare existing versions with currently available versions. Then the user would just need to click download to perform a grab of the zip file, remove the existing module and unzip the new one in its place. If the REST service also offered up install/uninstall/upgrade SQL then it could add any required DB changes to the site too. Not going to be easy, but it will be slick as f**k. |
| Messages In This Thread |
|
Update System - Best practice - by El Forum - 07-21-2009, 06:42 AM
Update System - Best practice - by El Forum - 07-24-2009, 06:09 PM
Update System - Best practice - by El Forum - 07-24-2009, 06:11 PM
Update System - Best practice - by El Forum - 07-28-2009, 03:35 AM
Update System - Best practice - by El Forum - 07-28-2009, 04:28 AM
|
