+- CodeIgniter Forums (https://forum.codeigniter.com)
+-- Forum: Archived Discussions (https://forum.codeigniter.com/forumdisplay.php?fid=20)
+--- Forum: Archived Development & Programming (https://forum.codeigniter.com/forumdisplay.php?fid=23)
+--- Thread: Update System - Best practice (/showthread.php?tid=20772)
Update System - Best practice - El Forum - 07-21-2009
[eluser]vlados2[/eluser]
Hi,
I am new to the community and hello to all
I am sure I will spend a lot of time here So
My first post will be to discus the best practices of building an auto update module/update server.Is it better to build an application with core and additional modules and update the core (like wordpress) or to build each file and track changes (somehow
) like a SVN, or to build a module to download the latest changes from the SVN What you think?
Update System - Best practice - El Forum - 07-24-2009
[eluser]xzela[/eluser]
Hi
I use SVN
It's easier to track changes and roll back files in case of accidents However, I'm just one developer working on a project. Of course
there are different (better? ) ways to do this.It really depends on what you are most comfortable with
good luck
Update System - Best practice - El Forum - 07-24-2009
[eluser]garymardell[/eluser]
sheish people that smiley face is controlling you. 13 of them in 2 posts!!!!
Update System - Best practice - El Forum - 07-28-2009
[eluser]vlados2[/eluser]
We are just happy people enjoying our lives
)))
Update System - Best practice - El Forum - 07-28-2009
[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.