|
-
Which web server do you use?
Which web server do you use?
Usually, I use Apache, but for low RAM environments, I use nginx which are both easy to manage!
-
-
I use Lighttpd on my servers; It's lite, fast and manages a lot of requests very nicely. I can't use Apache as it uses a lot of Memory and i'm really reserved on memory as of now.
Unlike Apache lighttpd dosen't have any .htaccess, instead it has a configurable file to allow or deny or manage redirections in it's own format of code.
-
-
I use Apache as it's easy to install and set-up, though I might have to start looking into lighttpd to save on resources etc... as resources are like gold, there worth a lot
-
-
Yeah, especially when you just have 256 Mb of RAM and you want to run a decent website, Lighttpd is pretty good at handling loads and requests. I've done a benchmark on it and it's somewhere up on this forum.
You can also try nginx which is equally good. Maybe run tests on them before you feel comfortable using them :P
-
-
nginx - it's a beast. It runs in under 10MB of RAM while still managing to run several resource-intensive community sites.
I used to use Apache, but nginx is so much simpler to configure and to keep running.
-
-
When choosing between Apache and Nginx (or others), it's not really an apples-to-apples comparison, so you better look at the feature-set carefully before you choose to move. Apache has tons of features and has a great ecosystem around it, which means it can do a lot more to help you generate the content you need - e.g. server-side processing. Nginx is more geared towards high-performance, yet simpler content serving needs. Identify your needs, and then choose.
In a nutshell, if you are using mod_php, mod_perl or any of the esoteric modules with Apache in your current installation, I think staying with httpd is a better idea. If you are facing performance problems, you could use Nginx as a reverse-proxy.
-
-
i'm using Apache most of the time for the server
-
-
Agree. Light is a very small web server. Can give a lot of pains. Better to work with apache, and allows servlets integration with tomcat very easy. For security porpouses better apache even more talking about ssl certs. Hope helps
-
-
Yea, i am completely agree with you,
You will have different options available but one should choose that is best to address their requirements.
 Originally Posted by paolochicha
When choosing between Apache and Nginx (or others), it's not really an apples-to-apples comparison, so you better look at the feature-set carefully before you choose to move. Apache has tons of features and has a great ecosystem around it, which means it can do a lot more to help you generate the content you need - e.g. server-side processing. Nginx is more geared towards high-performance, yet simpler content serving needs. Identify your needs, and then choose.
In a nutshell, if you are using mod_php, mod_perl or any of the esoteric modules with Apache in your current installation, I think staying with httpd is a better idea. If you are facing performance problems, you could use Nginx as a reverse-proxy.
-
-
Hello,
I use also Nginx which is easy to manage and can be optimized for a really good results. It also has a big community and support, but as was already said Apache has a lot of useful modules so it really depends on the needs. Basically If I can I use nginx because of the performance otherwise I use Apache
-
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Check out Linux Central for Linux software and other goodies!
» Recent Threads
» Stats
Members: 3,541
Threads: 3,912
Posts: 9,423
Top Poster: Fred (1,486)
» Links
|
Bookmarks