As I migrated to clean data layout (see previous post) I decided to be cool&trendy guy and fire up my own lovely cloudy service.<\/p>\n
First my thinking was bit off regular setup, because even if we have in-tree ebuild of owncloud it hard-requires apache, which I find overkill here.<\/p>\n
So I introduce you to secret approach how to make it work with ngnix and sqlite3. Before you say that I should use *insertothercooldbname* please think of that my deployment is only for handfull users and I tested it with 5 users connected at once each of them having access to 1 tb shared datastore and it proven fast enough.<\/p>\n
Well owncloud is testing, so unmask it:<\/p>\n
scarabeus@htpc: \/etc\/portage $ cat package.keywords\/own-cloud\r\nwww-apps\/owncloud<\/pre>\nWe need dav for direct access and php stuff for the setup (some useflags might be useless or redundant):<\/p>\n
scarabeus@htpc: \/etc\/portage $ cat package.use\/own-cloud\r\ndev-lang\/php pdo sqlite3 curl xmlwriter gd truetype cgi force-cgi-redirect fpm\r\nwww-servers\/nginx nginx_modules_http_dav<\/pre>\nNow silently punt the apache away as we love nginx:<\/p>\n
scarabeus@htpc: \/etc\/portage $ cat make.profile\/package.provided\r\nvirtual\/httpd-php-5.4<\/pre>\nAnd put all this to good use by emerging required stuff:<\/p>\n
emerge -v www-servers\/nginx www-apps\/owncloud<\/pre>\nSetting up the stuff<\/h2>\n
As nginx does not have any fcgi we will use the fpm from php directly. For that we need to add it to runlevel
rc-update add php-fpm default<\/code> and set up a bit default number of spawned servers (config is in\/etc\/php\/fpm-php5.4\/php-fpm.conf<\/code>). Also remeber to set there proper user\/group there, or you won’t be able to store content in your cloud, just read from it.<\/p>\nThen we set up the nginx (
\/etc\/nginx\/nginx.conf<\/code> and\/etc\/nginx\/fastcgi_params<\/code>). To keep this short and easy I will just post the config I used and let you to google for other nginx variables.
\nFirst the conf file:<\/p>\nserver {\r\n listen 80;\r\n server_name hostname;\r\n rewrite ^ https:\/\/$server_name$request_uri? permanent; # enforce https\r\n }\r\n\r\n server {\r\n listen 443;\r\n server_name hostname;\r\n\r\n ssl on;\r\n ssl_certificate \/etc\/ssl\/nginx\/nginx.crt;\r\n ssl_certificate_key \/etc\/ssl\/nginx\/nginx.key;\r\n\r\n access_log \/var\/log\/nginx\/htpc.access_log main;\r\n error_log \/var\/log\/nginx\/htpc.error_log info;\r\n\r\n root \/var\/www\/htpc\/htdocs\/owncloud\/;\r\n\r\n client_max_body_size 8M;\r\n create_full_put_path on;\r\n dav_access user:rw group:rw all:r;\r\n\r\n index index.php;\r\n\r\n location ~ ^\/(data|config|\\.ht|db_structure\\.xml|README) {\r\n deny all;\r\n }\r\n\r\n location \/ {\r\n rewrite ^\/.well-known\/host-meta \/public.php?service=host-meta last;\r\n rewrite ^\/.well-known\/carddav \/remote.php\/carddav\/ redirect;\r\n rewrite ^\/.well-known\/caldav \/remote.php\/caldav\/ redirect;\r\n rewrite ^\/apps\/calendar\/caldav.php \/remote.php\/caldav\/ last;\r\n rewrite ^\/apps\/contacts\/carddav.php \/remote.php\/carddav\/ last;\r\n rewrite ^\/apps\/([^\/]*)\/(.*\\.(css|php))$ \/index.php?app=$1&getfile=$2 last;\r\n rewrite ^\/remote\/(.*) \/remote.php\/$1 last;\r\n\r\n try_files $uri $uri\/ @webdav;\r\n }\r\n\r\n location @webdav {\r\n fastcgi_split_path_info ^(.+\\.php)(\/.*)$;\r\n fastcgi_pass 127.0.0.1:9000;\r\n include fastcgi_params;\r\n fastcgi_param HTTPS on;\r\n }\r\n\r\n location ~* ^.+.(jpg|jpeg|gif|bmp|ico|png|css|js|swf)$ {\r\n expires 30d;\r\n access_log off;\r\n }\r\n\r\n location ~ \\.php$ {\r\n fastcgi_split_path_info ^(.+\\.php)(\/.*)$;\r\n fastcgi_pass 127.0.0.1:9000;\r\n include fastcgi_params;\r\n fastcgi_index index.php;\r\n fastcgi_intercept_errors on;\r\n try_files $uri =404;\r\n }\r\n }\r\n<\/pre>\nFor the fcgi we also need some params to make the webdav work:<\/p>\n
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\r\nfastcgi_param SCRIPT_NAME $fastcgi_script_name;\r\nfastcgi_param PATH_INFO $fastcgi_path_info;<\/pre>\nThat should be it, now we just deploy the owncloud to our webserver by webapp-config:<\/p>\n
\/usr\/sbin\/webapp-config -I -h htpc -u root -d \/owncloud owncloud 4.0.7<\/pre>\nAfter we start up the webserver and fcgi provider, we should be up and running to open the stuff in web browsers.<\/p>\n
Few issues I didn’t manage to sort out in owncloud<\/h2>\n
\n
- External module to load all system users into it does not pass the auth<\/li>\n
- Google sync just timeouts everytime I try it (I maybe have just damn huge content here)<\/li>\n
- External storage support from within owncloud didn’t work for me, I just symlinked the data folder to the proper places under each user and logged into them in browser, then waited for 3 hours (1tb of data to index) and they were able to access everything.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
As I migrated to clean data layout (see previous post) I decided to be cool&trendy guy and fire up my own lovely cloudy service. First my thinking was bit off regular setup, because even if we have in-tree ebuild of owncloud it hard-requires apache, which I find overkill here. So… Continue reading