Should we add Lighttpd as an install/upgrade option?

Should we add Lighttpd as an install/upgrade option?

  • Yes, I would like to use lighttpd.

    Votes: 177 56.4%
  • I would like to use Nginx

    Votes: 66 21.0%
  • No, there are other things I would rather have.

    Votes: 71 22.6%

  • Total voters
    314
I think there is a problem here.

First the poeple voting are getting the same weight regardless of the amount of DA licences they use.
It's only a problem if JBMC (the company responsible for DirectAdmin) makes changes based on poll numbers.

Do you really think they do that?

Jeff
 
We take all info into account when making decisions. Poll numbers are only 1 factor of many, we usually put more weight on the discussion than the numbers. Also, we wouldn't be putting much of our own time into any development for this, we'd probably get a 3rd party to take on the project, so it wouldn't really affect our own coding. ;)

John
 
I think lighttpd is not so important, it's better to have a compiled version of Linux, like Gentoo.

I even can help with it :)
 
I'd rather see other options worked on then Lighttpd.

There are numerous other things that could be of assistance more than another web-server.
Also Lighttpd is missing core functionality that Apache delivers to date... I don't see it as a viable solution until they are supported.
 
II agree with user localhost.

Let's all switch to a system that requires a 30 to 50 hour compile every time we want to do something :D.

Jeff
 
Like compiling Freebsd for 6.2 for instance as its been sitting at 6.0 for a very long time.
 
Seriously, if people are after Nginx or lighttpd it would be easier of these individuals compiled it up themselves.

A HOWTO could be produced by DA staff to show them how to setup the logs so that the traffic is counted (similar to what they do for Apache).

Besides that I would prefer more effort placed on bugfixing, and feature enhancements to the core product. Lets not dilute the product on offer. ;)

Sure, for static content I think Nginx/lighttpd might be great (or even images, etc) but a howto can be provided for those interested in it.

I still see a need that Apache httpd will still required on many of the hosts that are running these alternate web-servers.
 
Hate to say it but a strong no from me as there is issues that need fixing first, all mostly minor but they soon add up.

1 - Unable to use latest zend optimiser because the DA panel is built against php4 and as such the plugins dissapeares so have to use old zend optimiser.
2 - Building binaries against old OS versions, FreeBSD 4.8 replace with the upcoming 7.0, change FreeBSD 5.1 (5.1 was beta) to 5.5, 6.0 to 6.3. Build static binaries as problems with the dynamic ones. Example have to use the 5.1 binary of exim since the 6 version is dynamic and the dependencyies are different.
3 - Integrate the FreeBSD ports system, this will take time to generate scripts that work with it but on the upside directadmin wont have to keep releasing binaries.
4 - Fix the problems with custombuild such as it overwriting the entire httpd.conf on every apache compile. Incorrect php flags been used.
5 - Finish all incomplete features and make the gui more complete.
6 - DNS multi server server system, the other week I had noticed changes on the primary DA server not copied over to the slave, I believe this was because at the time the changes were made the slave was down. Something needs doing where it checks for updates at intervals.
 
Last edited:
1 - Unable to use latest zend optimiser because the DA panel is built against php4 and as such the plugins dissapeares so have to use old zend optimiser.
No, you can use any version of php you want. Zend 3.3.0 sometimes does not work with php which is why you get no plugin output in DA. DA itself doesn't care what version of php is being used, hence we still include 3.2.8 (to prevent php from breaking)
2 - Building binaries against old OS versions, FreeBSD 4.8 replace with the upcoming 7.0, change FreeBSD 5.1 (5.1 was beta) to 5.5, 6.0 to 6.3. Build static binaries as problems with the dynamic ones. Example have to use the 5.1 binary of exim since the 6 version is dynamic and the dependencyies are different.
We always use static binaries when we can. The only reason we don't for newer systems is because the compilers won't let us due to linking with certain libraries and functions. Older systems allow us to create static binaries.

John
 
Ok so the 3.3 zend issue only is when php4 is used with apache? I think the machine in question had php 5 but I will try it out later see if I can upgrade zend and keep the plugins link.
 
I agree with all that say DA needs to be bug fixed first, before adding new applications.

Also a bug tracking system on this site would be a good feature! (Step 1 if you'd ask me!)

For those with a lot of servers, I'd like to request one more feature than already discussed. The update of DA itself, it must be a pain to have 100 DA servers and update them all. Wouldn't it be possible to have a "central update server", or a "master update server", that all "slave servers" could sync up with the master(s)?

you can add da update in corn day, week or month

Wael
 
Last edited:
Better add support for Subversion. It's always a hell to get it working with apache.
 
Honestly? If you're going to have lighttpd implemented, then at least have some sort of team work specifically on lighttpd so the main development will not cease. I can see many things in DA that need fixing, such as the naming convention for the scripts folder, as a member had already mentioned.
 
Back
Top