OwnCloud

install

1. get tar-ball or git or so...
2. unzip tarball
3. cp content to webserver (/var/www)
4. chown www-data:www-data /var/www/owncloud
5. allow overwrite (apache)
6. activate mod_rewrite
7. point browser to owncloud-dir (own vhost or subdir doesn matter)
8. follow install-wizard

problems

some problems i encountered during testing ownCloud-5-pre1-alpha (git)

file indexing

while i'm sym-linking some content directories of the system
from outside my owncloud-instance into it, i discovered they are sometimes not
displayed inside my clients for download.

solved it by manipulating my sqlite-DB.
(but should be the same for mysql or so...)

deleting all db-cached records, will OC force to re-scan filesystem:

$ sqlite3 /var/www/owncloud/data/owncloud.db
sqlite3> delete from oc_fscache [where user = 'USERNAME'];

mp3 ID-Tags

after linking some directories with mp3's into my owncloud instance
i discovered the badly set mp3 ID-Tags.
many songs simply didn't habe id-tags and so the owncloud music library
filed them unter the artists 'Unknown' which is correct from the view of the software!

but for humans it's hard to navigate and find songs...
i decided to set the correct artist-, title- and album- id-tags,
but OC didn't rescan, but loads old vals from DB... :-(

solved the same way. DB manipulation...

$ sqlite3 /var/www/owncloud/data/owncloud.db
sqlite3> delete from oc_media_songs;
sqlite3> delete from oc_media_artists;
sqlite3> delete from oc_media_albums;

since these tables have NO user-field you will have to delete ALL records
which results in rescan of media-app is required for all users...

See also

Mp3info set/get mp3 ID-Tags