Update 1 - one minor upgrade later, and they’re back to the previous
/usr/share/owncloud. Joy. Guess I’ll give it up.
Update 2 - ok, so unfortunately I didn’t give up, and wow 5.0.10 is
/var/www/. Double-you tee eff.
I’ve been trying out hosting my own ownCloud instance on one of my Debian servers, and it’s mostly gone pretty well, using their official apt repositories.
On around the 17th of July however, ownCloud published an update from version 5.0.8 to version 5.0.9 which completely broke the system as they changed where everything was installed to. I thought I’d write up a couple of pointers to getting things up and running again, if you’ve suffered the same problem.
Firstly, the application itself has moved from
a more conventional
/var/www/owncloud/. This means you’ll have to
update any Apache config you might have done to get it accessible. They
removed the original
/etc/apache2/conf.d/owncloud.conf, so if you were
relying on that, you’d have to create something new and correct in
/etc/apache2/sites-available/ and symlink it in
Next, the config configuration has also changed. Previously, the
owncloud/config/ directory used to be a symlink to
but now they have provided an actual config directory within the
ownCloud installation. I removed this directory, and created a symlink
Once that’s all set up, you should be able to load ownCloud in your browser and it should perform an upgrade on the DB. In my case, the upgrade process got stuck in a loop, I presume it’s setting a cookie that is not being cleared correctly. The “solution” was to restart my browser.
When you log in thereafter, all your stuff should be present as it were pre-upgrade.
It’s probably also a good idea to make regular backups of
/usr/share/owncloud/data/ - thank goodness this wasn’t wiped out with
the rest of the previous install location.