I think I know what you mean, I'm not sure how lighttpd works, but you should be able to match on the path to have config options specific to requests that start with ~ (or without ~)
The way werc is handled is via the dir-listing and the 404 handlers, so it should not interfere with the mod_userdir stuff, but what probably does interfere is setting the document root and the stuff to handle static files rather than werc-handled requests. Hope that made some sense, my grasp of the ligghtpd config arcana was always 'light', and luckily for my sleep I have forgot most of it. To be honest, I'm not even sure why/how your problem can happen, bu I think the config file system should allow to work around the problem. Hope this helps a bit, or that somebody more knowledgeable of lighttpd's peculiarities can enlighten us further.. uriel On Mar 3, 1:25 am, John Floren <[email protected]> wrote: > Hi > > I just set up werc + lighttpd on FreeBSD. My problem is that I > originally had lighttpd set up with mod_userdir enabled so my friends > could have stuff inhttp://jfloren.net/~user/. Now, however, werc > wants to try and locate that directory instead. Is there a way I can > specify that the user dirs "come first"? Hope I've explained things > clearly > > John -- You received this message because you are subscribed to the Google Groups "werc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/werc9?hl=en.
