Hot answers tagged lightweight
7
Have you considered installing Lighttpd? It sounds pretty much like what you need.
Also look at the package details for Ubuntu and the article on Softpedia. Possibly ignoring the PHP and MySQL references?
Edit: after installing the web server, do what RainyRat has suggested ;)
4
One of the easiest solutions to setup that performs considerably well in my opinion is nginx along with gunicorn.
For ''gunicorn'', you only need to do something like:
$ cd path/to/yourdjangoproject
$ gunicorn_django --workers=4
And a pretty standard nginx setup for this is
server {
...
location / {
proxy_pass http://127.0.0.1:8000;
...
4
Just get your periodic task to output the HTML files into a specific directory, then set that directory as your webserver's document root and make sure that the default document is set to (or at least includes) index.html. That way, when your task runs the "site" will be updated automatically.
2
Mysql always like RAM. Converting (at least most) of the tables (in joomla & moodle, not the others) to InnoDb format and increasing the memory that uses will help a great deal with the speed as well. innodb_buffer_pool_size is the mysql config. The default size that uses is just 8MB - if your database is really that small (and I'd frankly be a tad ...
2
thttpd is probably as small as I can think of without going into the in-kernel http servers like khttpd. It's not directly windows compatible, but someone came up with a version built in Cygwin.
2
I also think postfix is a good solution for you. If you find you need an easy to manage spam filter solution take a look at this: http://assp.sourceforge.net/
Checkout this great guide as well: http://howtoforge.com/virtual-users-and-domains-with-postfix-courier-mysql-and-squirrelmail-ubuntu-10.10
1
As you suspected, pretty much any webserver will handle your needs. My recommendation would be Apache as it is the most popular and most well known or lighttpd as it is very popular and a little more light weight but still full featured.
If you need the entire stack, go with Linux. Especially Red Hat Enterprise Linux if you are spending the money and need ...
1
For monitoring with Nagios etc. you just need a small client on the monitored machine that communicates with the real nagios installation. No database or web server necessary, at least on the clients.
Other options would be built-in performance monitor of Windows (which can be queried remotely) and SNMP (part of the OS, but not installed by default).
1
Use Apache and disable the modules you don't need and ensure that you're not spawning too many processes to begin with.
The idea that Apache's core is somehow heavyweight is somewhat of a myth - it can be as beefy or lightweight as you need it to be, thanks to the modular design.
This has the added benefit of working with your existing distribution ...
1
You are correct in that the upgrade tool is for older access points than the one you have. On the newer access points you can just tftp a lightweight firmware image. The difference is the newer access points have a "manufacturer installed certificate" or MIC burned into the flash. The conversion tool creates the certificate on the older access points. ...
Only top voted, non community-wiki answers of a minimum length are eligible
