Dolphin htaccess rules for lighttpd server

Hi I am deploying on a non-.htaccess supporting server called lighttpd which is quite amazing with performance.

All static links are working fine, but the user profiles pages, search pages, and all the dynamic SEO'ed pages show a 404 error. So Staff/Helping members please post a rewrite rules set compatible to lighttpd so it can work.

I really wonder not much people using lighttpd here, which is actually way better in performance and less in resources.

Thanks.

PS: somebody Please post your standard .htaccess too

same problem here

my current production system is supporting 300+ simultaneous connections. the setup is classic lighttpd load balancer, mysql write-only master, multiple mysql read-only slaves, bunch of fast-cgi backends

is dolphin deployable for this architecture? if so, please indicate where the configuration can be found, many thanks

If the server does not support .htaccess then why are you asking for a compatable replacment? No htaccess support means just that. So no amount of tinkering with the .htaccess file is going to do anything if the server does not process it.

Not many use lighttpd because the dolphin server requirements specify apache. And .htaccess support is one of the reasons why.

It's runs faster because it has less features.

The workaround is shutting off permalinks support. Advance settings in your dolphin admin.

the workaround fixed the 404 errors for members but did not fix the 404 errors for main menu

Sorry, your right. Admin->Setting->Permalinks.  Nothing under advanced. So you did it right.

As for whether or not there will be other problems i can't provide a answer. I use servers that run apache, so i don't run my sites with no htaccess support, so i do not know if there are additional problems.

You aparently edited your post while i was responding.

You may need to go into the menu builder and move a couple of items around and then back to their origional positions to force dolphin to rebuild the menus.

thanks for the help 

 This is a very old post but I have to respond to this because practically everything you state here is completely wrong.

.htaccess was developed as an easy way for hosting companies to allow special rules and have that rules file inside the actual website files for access through stuff like cPanel or Plesk. Boonex is probably used mostly on shared hosting servers, so for most people this makes sense.

Buy Boonex is NOT tied to Apache because of this or any other reason. Web servers are web servers and regular expressions are regular expressions. Boonex specifies Apache simply because of native support for .php which Windows boxes do not support out of the box, and Apache is the default web server install on most flavors of Linux. Every other Linux web server ever created does support .php, and the Boonex devs simply didnt bother to translate the rewrite rules, which only took me about 30 minutes to do and are posted here:

http://www.boonex.com/forums/#topic/lighttpd-rewrite-rules.htm

As I said, regular expressions are regular expressions. Apache just has a different syntax requirement than Lighttpd or nginx does. For instance, quotes are required in lighttpd around the paths.

Thats actually a bit irritating that they did not take the time to do this. We have a premium platform here, and you cannot use a premium server such as lighttpd or nginx out of the box. I wouldnt be surprised if many large sites do not transition to Boonex for this reason alone, not to mention quite a few others I could name. Lighttpd is a far better hosting platform than Apache is for dedicated servers hosting 1 or 2 high volume sites.