While the documantation clearly states that to update ownCloud you should move away the old sources and copy over the config we keep seeing issues on github where the root cause of whatever problem the reporter describes has been caused by overwriting the old sources with the new ones. Sometimes, that may leave files in place that get picked up by the classloader or some css / js magic.
To try and hopefully prevent issues caused by this (more often) I propose to add the version suffix to the owncloud folder in the release tar/zip. Personally, I have set up apache to serve ownCloud from a symbolic link. Whenever there is an update I unpack the release tarball,
mv owncloud owncloud-x.y.z, copy the old config, put old oc in maintenance via occ, update the symbolic link, update the now oc, switch to single user mode, test, allow all users to log back in. So far I have not had the need to restore a database backup (coming from oc4.0), but that may have been luck. In that case I can also easily switch back by changing the symbolic link again.
Anyway, what is your opinion? Should we add a version suffix to the ownCloud folder in the release tarball?
- Nah, keep the folder name 'owncloud'.
- Yes, please! It will save me an extra
mvon every update. Maybe, it will even prevent mixed codebases and save people countless hours of hair pulling, trying to reproduce a weird issue.
Votes are public.
Or is there another option?