Hi Casey, <br><br>Robert Krahn (@HPI) recently created a <a href="http://www.lively-kernel.org/repository/lively-wiki/users/robertkrahn/rk-installInstructions.xhtml" target="_blank">video illustrating setup</a>.<br>
<br>Below are some old detailed instructions I compiled for my own use last spring along with an Apache config file. These instructions were for Linux.<br><br><b>1. Instructions</b><br><br>Preparing Apache for Lively<br>
<br>These steps were performed for Linux under Ubuntu 8.04 HardyHeron running at <a href="http://slicehost.com" target="_blank">slicehost.com</a>. Connecting to the machine as root using ssh from Mac OS X 10.5.6<br>
Caveats:<br>The version of Apache was having trouble with digest authentication so this setup example is using basic authentication only. The recommendation is to use something better than basic authentication.<br>Apache modules may be configured permanently (a2enmod) or at runtime in httpd.conf (LoadModule). When I rehearsed these steps for this writeup, I did not get LoadModule working reliably quickly for WebDav so I stopped. <br>
Running as root I think is a bad idea but I did it for this writeup.<br><br># connect, update the system, and install the Apache web server<br>ssh <username-or-root>@<host><br>sudo apt-get update<br><br>sudo apt-get install apache2<br>
a2enmod dav<br>a2enmod dav_fs<br>a2enmod auth_digest<br>a2enmod proxy<br>a2enmod proxy_http<br>a2enmod rewrite<br><br>apt-get install subversion<br>cd /var<br>mkdir lively-kernel<br>cd lively-kernel<br>svn checkout <a href="http://livelykernel.sunlabs.com/repository/lively-kernel/trunk/" target="_blank">http://livelykernel.sunlabs.com/repository/lively-kernel/trunk/</a><br>
# copy the kernel client files to web document root - this will force overwrite the existing Apache index.html page (warning!)<br>cp -rf trunk/source/kernel/* /var/www<br><br># these commands ensure that WebDav has permissions for Apache's document root<br>
cd /var<br>chmod -R 755 www<br>chown -R www-data www<br>chgrp -R www-data www<br># important caveat: if you later manually upload files, for example using ftp and not WebDav, you likely need to issue these again<br><br># create username and password for WebDav access<br>
htpasswd -c /etc/apache2/access <webdav-username><br># otherwise auth digest would be like: htdigest -c /etc/apache2/access global <webdav-username><br><br># edit the web server configuration with httpd.conf source<br>
# if you are not familar with the vi editor it will likely be easier just to upload httpd.conf using an ftp client<br>vi /etc/apache2/httpd.conf<br><br># run or reload the web server<br>sudo /etc/init.d/apache2 restart<br>
# sudo /etc/init.d/apache2 force-reload<br><br># now configure the Lively install<br># pending<br><br><b>2. Apache httpd.conf file</b><br><br><VirtualHost *><br> ServerAdmin <a href="mailto:you@yourdomain.com" target="_blank">you@yourdomain.com</a><br>
ServerName <a href="http://yourdomain.com" target="_blank">yourdomain.com</a><br> ServerAlias <a href="http://www.yourdomain.com" target="_blank">www.yourdomain.com</a><br> <br> DocumentRoot /var/www<br> <Directory /var/www><br>
Options Indexes MultiViews<br>
AllowOverride None<br> Order allow,deny<br> allow from all<br> </Directory><br> <br> <Location /><br> DAV On<br> AuthType Basic<br> AuthName "Restricted Files"<br>
AuthUserFile /etc/apache2/access<br> <LimitExcept GET OPTIONS PROPFIND><br> Require valid-user<br> </LimitExcept><br> </Location><br> <br> <Proxy *><br> Order deny,allow<br>
Allow from all<br> </Proxy> <br> <br> # see also: trunk/source/kernel/example.htaccess & example.htpasswd<br> # consider the implications of all of these proxies before hosting a public site<br>
RewriteEngine On<br> RewriteRule ^/proxy/<a href="http://news.com.com" target="_blank">news.com.com</a>(.*)$ <a href="http://news.com.com" target="_blank">http://news.com.com</a>$1 [P]<br> RewriteRule ^/proxy/<a href="http://news.cnet.com" target="_blank">news.cnet.com</a>(.*)$ <a href="http://news.cnet.com" target="_blank">http://news.cnet.com</a>$1 [P]<br>
RewriteRule ^/proxy/<a href="http://weatherforecastmap.com" target="_blank">weatherforecastmap.com</a>(.*)$ <a href="http://weatherforecastmap.com" target="_blank">http://weatherforecastmap.com</a>$1 [P]<br> RewriteRule ^/proxy/<a href="http://feeds.bbc.co.uk" target="_blank">feeds.bbc.co.uk</a>(.*)$ <a href="http://feeds.bbc.co.uk" target="_blank">http://feeds.bbc.co.uk</a>$1 [P]<br>
RewriteRule ^/proxy/<a href="http://finance.google.com" target="_blank">finance.google.com</a>(.*)$ <a href="http://finance.google.com" target="_blank">http://finance.google.com</a>$1 [P]<br> RewriteRule ^/proxy/<a href="http://download.finance.yahoo.com" target="_blank">download.finance.yahoo.com</a>(.*)$ <a href="http://download.finance.yahoo.com" target="_blank">http://download.finance.yahoo.com</a>$1 [P]<br>
RewriteRule ^/proxy/<a href="http://feeds.feedburner.com" target="_blank">feeds.feedburner.com</a>(.*)$ <a href="http://feeds.feedburner.com" target="_blank">http://feeds.feedburner.com</a>$1 [P]<br> RewriteRule ^/proxy/<a href="http://blogs.sun.com" target="_blank">blogs.sun.com</a>(.*)$ <a href="http://blogs.sun.com" target="_blank">http://blogs.sun.com</a>$1 [P]<br>
RewriteRule ^/proxy/<a href="http://feeds.tuaw.com" target="_blank">feeds.tuaw.com</a>(.*)$ <a href="http://feeds.tuaw.com" target="_blank">http://feeds.tuaw.com</a>$1 [P]<br> RewriteRule ^/proxy/<a href="http://api.flickr.com/services/rest/" target="_blank">api.flickr.com/services/rest/</a> <a href="http://api.flickr.com/services/rest/?api_key=YOUR_KEY" target="_blank">http://api.flickr.com/services/rest/?api_key=YOUR_KEY</a> [QSA,P]<br>
</VirtualHost><br><br><br><div class="gmail_quote">On Thu, Apr 22, 2010 at 7:47 PM, Casey Ransberger <span dir="ltr"><<a href="mailto:casey.obrien.r@gmail.com" target="_blank">casey.obrien.r@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Any recommendation for DAV setup on UNIX and company?<div><br></div><div><br>-- <br>Casey Ransberger<br>
</div>
<br>_______________________________________________<br>
lively-kernel mailing list<br>
<a href="mailto:lively-kernel@hpi.uni-potsdam.de" target="_blank">lively-kernel@hpi.uni-potsdam.de</a><br>
<a href="http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel" target="_blank">http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel</a><br>
<br></blockquote></div><br>