« [Naming poll] Stylings
Wedge on lighttpd or nginx
So this is where you folks have been hiding »

sokha

  • ola alo
  • Posts: 14
Wedge on lighttpd or nginx
« on June 30th, 2011, 02:27 PM »
I guess wedge will sooner or later be in public. I know many people use apache webserver but I prefer to use lighttpd instead. As I read in the FAQ, it says:
Quote
Server side:

PHP 5.1.2 or higher, 5.2 or higher recommended
MySQL 4.1.2 or higher, 5.0 or higher recommended
GD2 graphic library for PHP
I would like to ask will wedge work 100% on lighttpd?

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge on lighttpd or nginx
« Reply #1, on June 30th, 2011, 03:53 PM »
lighttpd, yes, seeing how it is intended to be 100% compatible with Apache. Have they fixed the ridiculously crippling memory leaks yet?

nginx is a different story altogether, and it's possible the pretty URLs code will need tweaking to work on it.
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Wedge on lighttpd or nginx
« Reply #2, on June 30th, 2011, 04:48 PM »
Our pretty URLs shouldn't need much work. It's just a matter of changing one line basically... And I'm sure it has some suitable replacement for it ;)

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge on lighttpd or nginx
« Reply #3, on June 30th, 2011, 05:05 PM »
That's not what I was thinking of. nginx doesn't use .htaccess files AT ALL. The entire way of setting up routing is different.

CJ Jackson

  • I got myself a new iPad, a different world to the iPhone!
  • Posts: 241
Re: Wedge on lighttpd or nginx
« Reply #4, on June 30th, 2011, 05:17 PM »
As for IIS7, it has url rewrite and web.config, also it has a converter that convert mod-rewrite to url rewrite rules, so it should work on IIS7 with no problem.

sokha

  • ola alo
  • Posts: 14
Re: Wedge on lighttpd or nginx
« Reply #5, on July 8th, 2011, 11:53 AM »
Since I am not php coder, I have a question. Is it possible to handle the fancy URL in php code instead of .htaccess or in webserver?

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge on lighttpd or nginx
« Reply #6, on July 8th, 2011, 12:47 PM »
No.

The .htaccess file is the part that handles the fancy URL and passes it to PHP.

You can, on some configurations, get around it by constructing URLs in the form of index.php/rest-of-link/whatever but it's ugly and unreliable.

CJ Jackson

  • I got myself a new iPad, a different world to the iPhone!
  • Posts: 241
Re: Wedge on lighttpd or nginx
« Reply #7, on July 8th, 2011, 01:12 PM »
Quote from Arantor on July 8th, 2011, 12:47 PM
The .htaccess file is the part that handles the fancy URL and passes it to PHP.
Actually it's the Apache module called "mod_rewrite" that does that, all .htaccess does is store the configurations for Apache and it modules (including "mod_rewrite") per directory.  :eheh:

Same applies with IIS, URL Rewrite and web.config.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Wedge on lighttpd or nginx
« Reply #8, on July 8th, 2011, 01:32 PM »
Quote from Arantor on July 8th, 2011, 12:47 PM
No.
I'd say yes, actually... You'll still need to edit .htaccess or httpd.conf once, but once it's done it's done.
Just redirect all missing files to index.php, either through ErrorDocument 404 (very bad idea since it fills the error log instead of the access log), or a rewrite rule on -f and -d parameters (missing file/folder).
Wedge comes with its own pre-made .htaccess with includes these for our pretty url implementation.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge on lighttpd or nginx
« Reply #9, on July 8th, 2011, 02:10 PM »
Quote from CJ Jackson on July 8th, 2011, 01:12 PM
Quote from Arantor on July 8th, 2011, 12:47 PM
The .htaccess file is the part that handles the fancy URL and passes it to PHP.
Actually it's the Apache module called "mod_rewrite" that does that, all .htaccess does is store the configurations for Apache and it modules (including "mod_rewrite") per directory.  :eheh:

Same applies with IIS, URL Rewrite and web.config.
Yes, I know that. I was keeping the answer as straightforward as possible.
Quote
I'd say yes, actually... You'll still need to edit .htaccess or httpd.conf once
Then the answer IS no. The question asked was whether it could be done without .htaccess, which other than the index.php/url structure, pretty URLs cannot be done *just* in PHP, it relies on the web server routing properly.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Wedge on lighttpd or nginx
« Reply #10, on July 8th, 2011, 02:50 PM »
I was just answering to his question in case he phrased it badly, i.e. he wanted to know if new URL schemes could be added without rewriting the htaccess itself (since it requires some prior knowledge). In PHP at least you can do without regex, even if it's strongly recommended to use them.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge on lighttpd or nginx
« Reply #11, on July 8th, 2011, 02:53 PM »
Hmm, well, I've come to the conclusion of assuming the lowest common denominator as far as anyone is concerned these days: if someone is interested in the finer points, they'll probably ask in a way that suggests it - while if someone asks a broad question, they probably don't want details.

Yeah, it's nice that it's extensible without having to be complicated in terms of editing the htaccess file now.

sokha

  • ola alo
  • Posts: 14
Re: Wedge on lighttpd or nginx
« Reply #12, on July 9th, 2011, 12:45 AM »
Quote from CJ Jackson on July 8th, 2011, 01:12 PM
Quote from Arantor on July 8th, 2011, 12:47 PM
The .htaccess file is the part that handles the fancy URL and passes it to PHP.
Actually it's the Apache module called "mod_rewrite" that does that, all .htaccess does is store the configurations for Apache and it modules (including "mod_rewrite") per directory.  :eheh:
I ever knew and work with .htaccess of apache for a while. Yes, .htaccess work only with apache as far as I know.
Quote from Nao/Gilles on July 8th, 2011, 01:32 PM
Quote from Arantor on July 8th, 2011, 12:47 PM
No.
I'd say yes, actually... You'll still need to edit .htaccess or httpd.conf once, but once it's done it's done.
Just redirect all missing files to index.php, either through ErrorDocument 404 (very bad idea since it fills the error log instead of the access log), or a rewrite rule on -f and -d parameters (missing file/folder).
Yes, this is what I was thinking.
Quote from Nao/Gilles on July 8th, 2011, 01:32 PM
Quote from Arantor on July 8th, 2011, 12:47 PM
Wedge comes with its own pre-made .htaccess with includes these for our pretty url implementation.
I ever used apache2 before. At my site, there are plenty files to download and stream (audio). Before, apache always ate all of my server CPU and memory. I can't figure out how to tweak it (I used mod_php). Since it is hard to optimize, then I switched to lighttpd. It works perfectly as I need.

Nao

  • Dadman with a boy
  • Posts: 16,082

[Unknown]

  • Posts: 77
Re: Wedge on lighttpd or nginx
« Reply #14, on July 9th, 2011, 08:31 AM »
It's a common configuration to have all non-existent URLs forwarded to PHP.  I know that lighttpd also supports X-Sendfile, so technically I guess you could forward ALL requests to PHP even.

Although this does require configuration, basically most other PHP packages require it too, so it doesn't seem like a hefty requirement.  Falling back to pathinfo (index.php/xyz) is easy enough, too.

Note that many nginx and lighttpd servers are configured to disallow pathinfo requests because of some gotchas in configuring them with PHP.  There are correct ways to configure them with pathinfo working, but many people don't do this.  So, pathinfo actually becomes the less universal solution.

-[Unknown]
« [Naming poll] Stylings
So this is where you folks have been hiding »