On 10.06.2012 21:36, Paul van Tilburg wrote:
> Hi!
Hi!
>
> Do you mean by a fully new installation an installation using the released
> tarball from upstream?
>
I meant: clean new debian package with lighty. I am running the upstream
tgz and wanted to change to the debian package. But I knew from former
upgrades that there are problems with data/ and config/ so I thought
that the problems occured by copying the running upstream to an backup
directory, install the debian package and then copy data and config
stuff to the right place. But after the problem occured I reinstalled
the debian package again and tried out the package without the old data
from my upstream installation. And this "clean" installation had the
problem too.
>> footnote1:
>> lighty configuration for owncloud (works with stock owncloud tarball):
>>
>> alias.url += ( "/owncloud/" => "/var/lib/owncloud/" )
>>
>> $HTTP["url"] =~ "^/owncloud/data/" {
>> url.access-deny = ("")
>> }
>>
>> $HTTP["url"] =~ "^/owncloud($|/)" {
>> dir-listing.activate = "disable"
>> }
>
> Given the .htaccess file that is shipped with ownCloud 4,
>
> I am actually not aware whether lighttpd can read and use .htacess
> files. If not, given the .htaccess file that is shipped with ownCloud
> 4, I am not sure that just the above three directives are enough to get
> it working.
>
Lighty does not know anything about .htaccess. The config above is the
offical config for lighty from the upstream documentation (mostly
security stuff only the first line is needed to get it run with the
upstream tarball.
So the configuration is tested with my actual running upstream tarball
with no problems. Because the debian packages looks like the original
(with the symbolic links pointing to /usr/share...) this should work
with the debian packages too.
> Cheers,
> Paul
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
