ownCloud 8.0.0 preliminary testing for Fedora 21 / 22

Hey folks!

For any ownCloud'ians out there; I worked some more on the OC 8 packages for Fedora today and I think they're in reasonably testable shape now. I just updated my production deployment and it worked first time.

IMPORTANT: back up really, really carefully before testing these out. They should work, but I want to get more testing to be sure. This is what you'll be doing. Please, please make sure beforehand that if the upgrade breaks completely, you have everything you need to recover. Ideally, test these on a dev instance or test machine or something.

Please ensure you have this line in /etc/owncloud/config.php before updating:

 'check_for_working_htaccess' => false,

or else the OC updater will refuse to run. I will probably add a belt-and-braces fix for this later, but it's a good idea to have that set in any case. It has been part of the default config in the package for some time, but very old installations may not have it.

If you have edited /etc/httpd/conf.d/owncloud.conf at all please merge in the changes from the package before attempting to access the server. There are substantial changes in the Apache config files. I have tried to make them easier to work with. If all you need to do is make the OC installation accessible (override the config that makes it only accessible from localhost out of the box), you do not need to modify owncloud.conf at all, all you have to do is:

ln -s /etc/httpd/conf.d/owncloud-access.conf.avail /etc/httpd/conf.d/z-owncloud-access.conf

if you previously enabled global access in any other way I recommend switching to this one, as it will ensure things keep working in future without you needing to do anything, but you can see the directories you need to allow access to in that file if you want to do it any other way. /var/lib/owncloud/apps must be allowed and must be Aliased to /owncloud/appstore-apps (or else installing apps from the 'app store' won't work, and you're really going to need it to, see below). /var/lib/owncloud/assets should be allowed and should be Aliased to /owncloud/assets (though this only matters if you enable the asset-pipeline.enabled setting in config.php).

Please keep owncloud.conf (and all the .inc files in the package) unmodified if at all possible, and use a separate file to make any overrides you want to the configuration. This way when I need to update owncloud.conf in future you will get the changes automatically.

After upgrading you will find that most of your apps have disappeared. Don't panic! ownCloud just decided to move a lot of apps that were previously shipped in the tarball (including even Contacts and Calendar) into the 'app store'. You can go into the 'Apps' screen as an admin user and enable the apps you need. When you enable them, all your existing data and configuration for them should reappear, they will not be blank.

I am considering whether to provide packages for some of the core apps or even add them back to the ownCloud package itself, but for now, installing them from the app store should work fine - as long as you followed the instructions above about making sure the Apache config snippets are up to date.

The packages are available in my side repo for Fedora 21 and 22 (I've symlinked 22 to 'rawhide' as well, as the 22 builds should probably work for Rawhide). Get the repo file and place it in /etc/yum.repos.d to enable the repo.


Dan Mossor wrote on 2015-04-18 19:55:
Just curious, why aren't your packaging efforts in the main repos? Is ownCloud encumbered?
adamw wrote on 2015-04-21 00:22:

They are. I keep a side repo for doing various things I don't want to put in the main repos (like very early builds of new major releases, and pre-flight tests before I send builds to Bodhi, and stuff like that).

Momcilo Medic wrote on 2015-08-22 00:03:
Really nice post explaining proper way of doing things. Can I ask what would be the proper way of moving owncloud to the root URL instead of /owncloud ? I am using Fedora Server 22.
adamw wrote on 2015-08-22 00:08:

I've never actually done that and wouldn't want to suggest it offhand. You can achieve the basic change by just changing the Apache config, but ownCloud might need config changes, I don't recall offhand all the ways it uses the paths.

Momcilo Medic wrote on 2015-08-22 00:18:
Oh ok, thanks. My intent is to use it as a subdomain (https://owncloud.example.com). At least I know there is no recommended way and I need to pay extra attention when updating. Still, awesome post. Thanks Adam ;)
adamw wrote on 2015-08-22 00:48:

If you try it out and figure out all the bear traps, let me know and I'll write it up (and try to fix any that are bugs :>)