You are not logged in.
I have a simple site that I would like to host on a machine with minimal resources. What is my best bet?
lighttpd and nginx sell themselves as being lightweight in high traffic environments... But this is not a high traffic environment.
Apache seems like overkill.
thhtpd seems to be what I'm looking for, however the last release was in 2003, and I find that worrisome.
Can anyone offer me any insight?
Last edited by gabe_ (2011-05-19 20:41:39)
Offline
I have a netgear wireless router running Tomato. It hosts my local repo for a number of machines. I use lighttpd which is incredibly light weight. Lighttpd is my suggestion.
Last edited by graysky (2011-05-19 20:46:34)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I'd go with nginx- it is as lightweight as you will get and good for in any environment. The exception would be on something like a router; I'd probably go with the httpd built into busybox if I needed something super lightweight (but also severely limited in functionality compared to nginx).
Offline
Agree with toofishes.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Interesting - I didn't realize BusyBox included an httpd. I've always thought of it as "coreutils for people who want to install Linux on a toaster."
To give some more information, I am building a MAME Cabinet. In addition to playing games, I'm considering using the machine to serve up a simple website with some information about the cabinet - mostly as a novelty.
I want to keep things light because I'm a raging minimalist, but also because I want the bulk of the machine's meager resources to be available for gaming.
Offline
There is also darkhttpd, in the repos, very small and simple.
Offline
That's a language propblem. You assume that having a high traffic environment is a dependency for their "lightweigtness". You should understand the sentence as "lightweight, even in high traffic environments".
Offline
I've always been a fan of lighttpd. Mostly just personal preference for the syntax of the config file. Easy to use/understand and tons of documentation. I've heard some good things about nginx but there were some things I just couldn't get working properly, and I also think the way you define virtual hosts was way too cumbersome. In my lighttpd file it's just a single line I need to add.
[home page] -- [code / configs]
"Once you go Arch, you must remain there for life or else Allan will track you down and break you." -- Bregol
Offline
gabe_ wrote:That's a language propblem. You assume that having a high traffic environment is a dependency for their "lightweigtness". You should understand the sentence as "lightweight, even in high traffic environments".
Not necessarily (though I do see your point).
I know that they are "full featured" httpd's. One of those features is being able to serve dynamic content across thousands of simultaneous connections. I realize I'm splitting hairs here, but I don't need those features. For this reason, I'm highly considering darkhttpd (thanks for the tip, Wittfella).
Offline