On Sun, Oct 14, 2018 at 11:17:20AM +0200, KatolaZ wrote: > On Sun, Oct 14, 2018 at 11:05:20AM +0200, aitor_czr wrote: > > [cut] > > > On the other hand, the configuration suggested by KatolaZ: > > > > http://pkgmaster.devuan.org/devuan_mirror_walkthrough.txt > > > > that is: > > > > RewriteEngine on > > RewriteRule /devuan/merged/pool/DEVUAN/(.*) /devuan/pool/$1 > > RewriteRule /devuan/merged/pool/DEBIAN-SECURITY/(.*) > > /debian-security/pool/$1 > > RewriteRule /devuan/merged/pool/DEBIAN/(.*) /debian/pool/$1 > > > > didn't work for me. I just shared the one which worked in my server, using > > Redirect 302. > > > > Dear Aitor, > > could you please elaborate on that? Many Devuan mirrors are using > apache and they have used the same walkthrough. If there is anything > we should change/improve in the walkthrough, it would be good to know.
nginx or apache? There are others. This may be moot because I don't have the resources for a Devuan mirror anyway (just a home DSL line), but I use lighttpd. Do I guess correctly that every web server would have to be configured completely differently and that it's a mug's game to try and handle all these possibilities in one document? The rumour mill for the past few years suggests that apache is overcomplicated and thus vulnerable. Is this an issue? Or are the complications actually needed for something like setting up a distro? And is this also true for nginx? I haven't heard much about that one. -- hendrik. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
