New build system (BETA)

I have to agree with Big Wil here. For me, the biggest reason I never upgraded to apache 2.x is that I would lose FrontPage extensions, and from what I have read, DA doesn't support WebDav yet.
 
donkeyKICK said:
I have to agree with Big Wil here. For me, the biggest reason I never upgraded to apache 2.x is that I would lose FrontPage extensions, and from what I have read, DA doesn't support WebDav yet.
Click to expand...

I used to run Apache 2 with mod_frontpage quite well. I don't see why it wouldn't still run it. They actually got rid of the need for our frontpage patch when they put out Apache 2 which was nice but we still needed the patch to run another engine so we haven't been able to upgrade all servers to AP2 and actually had to go back to AP1.

iceuk626 said:
DENY directives still work as normal with suPHP
Click to expand...

Ok. I thought that suPHP refused to process .htaccess files. That is the impression I got but maybe I misread. So then there are just certain things that it refuses to process within the .htaccess files?

Big Wil
 
BigWil said:
Ok. I thought that suPHP refused to process .htaccess files. That is the impression I got but maybe I misread. So then there are just certain things that it refuses to process within the .htaccess files?
Click to expand...

"php_value" and "php_flag" directives are the only things that don't work, but there is a PECL extension (htscanner) that allows the use of these flags in .htaccess using PHP fastCGI and suPHP.
 
Far as I'm concerned...and this is just me...could care less about mod_frontpage...actually I've went out in the street and did a jig when it was removed. I've already informed my clients that I no longer support it and that if they wish to continue to use it, they can only use it as a WYSIWYG editor...that the FP proprietary "goodies" and "publish" features are not supported. They can learn to actually code HTML and use FTP or find a Windows host. This seems harsh? it is. But tired of spending 80% of time supporting 10% of the clients for something thats (IMHO) as uptodate as DOS edlin.

As for the other issues...

DA needs to get on the ball and stop dragging it's feet on AP2/PHP5. The excuse of "well, PHP4 still works, so no need to rush to PHP5" etc is bull. Get with the program. Users want PHP5...users WANT mysql5. They are no stable and the defacto new standards. This is the area that DA needs to concentrate on and stop using excuses before DA turns into HSphere (worlds biggest crap of a CP).
 
I think maybe you have been looking in the wrong place. RTR has the extensions to run with AP2 at least they used to. Of course now they are no longer allowed to let anybody download them nor can anybody who already has them redistribute them. So I guess you are right. No more mod_frontpage for Apache 2 or even 1 for that matter.

Looking over the licensing it doesn't look like anyone can redistribute mod_frontpage for use with ANY server now. John might want to look into this quickly.

Big Wil
 
Ok. Well I can claim completely ignorant on that one. We stopped running Apache 2.anything when we started using DA back in 2004. I am looking forward to getting back to it one day. Guess we will just stick with 1.x for awhile longer.
 
I'll just chime in here. This product is for you guys, so what you want, you get ;) The fact remains that pretty much every single admin has different needs, so we do our best to accomodate what everyone wants. Custombuild does have frontpage in it at the moment for apache 1.3. I believe we could add frontpage into apache the 2.0 if desired, but as smtalk said, 2.2 won't work with it no matter what.

For php4/5 and mysql4/5 ... we include mysql 5 for any new OS we add support for. The php4/5 issue, a lot of script still don't support php5, which is going to have to change eventually. We will probably continue to offer php4 forever (at the moment), but we have the task of playing a fine balancing act with user wishes, compatibility, new technolgies, old technologies, and stability.

Adding options is probably the easiest way to go about it. Although making everything more complex, in the end will probably make everyone happier.

John
 
Hi,
There's a small bug while compiling php under CentOS 5 x86_64. It's related with mysqlclientlib:
gcc: /usr/lib64/mysql/libmysqlclient.so: No such file or directory
make: *** [libphp5.la] Error 1
Click to expand...

Since the libmysqlclient.so can be found at /usr/lib64/ and not /usr/lib64/mysql/ (At least for mysql 5) i guess the php 'configure' line should be changed.
 
My bad :)

Anyway after each mysqlclient update we'll need to copy it again so i think that a sym-link would be better:

Code: 
ln -s /usr/lib64/mysql/libmysqlclient.so /usr/lib/libmysqlclient.so
 
I've been doing:
Code: 
ln -s ../libmysqlclient.so /usr/lib64/mysql/libmysqlclient.so
Because there is a 64-bit version in /usr/lib64/libmysqlclient.so.

John
 
There is also the issue with httpd.conf preservation.

customapache appends to the file changes it needs to make preserving current configuration whilst custombuild copies a new file over it. A request for smtalk to add a simple y/n to allow admins to not have their config overwritten fell on deaf ears. There is also other problems with custombuild, a new server installation I did only a couple of weeks ago still shows it has issues on a new install of directadmin the installation doesnt complete so I had to revert to customapache and even when I installed custombuild again after that I see the suphp configuration still isnt quite right.
 
DirectAdmin Support said:
The fact remains that pretty much every single admin has different needs, so we do our best to accomodate what everyone wants.
Click to expand...

Hey, you have done a great job doing just that the last 3 years. I haven't been disappointed.

DirectAdmin Support said:
Custombuild does have frontpage in it at the moment for apache 1.3. I believe we could add frontpage into apache the 2.0 if desired, but as smtalk said, 2.2 won't work with it no matter what.
Click to expand...

Did you all try the RTR patched distribution that used to work for 2.0? It has been a few years since I was on the AP2 beta group but something in the back of my mind reminds me that even when they said that version would no longer work with newer than 2.0 it did in fact work. Of course they don't distribute it anymore so one would have to find someone that has a copy. Might be impossible, might not, might not even be worth it. Just throwing it out there.

DirectAdmin Support said:
For php4/5 and mysql4/5 ... we include mysql 5 for any new OS we add support for. The php4/5 issue, a lot of script still don't support php5, which is going to have to change eventually.
Click to expand...

I think 4 and 5 should be options but 4 should be the default in both cases. PHP5 has the script compatibility issues plus every 12 year old cracker out there is trying to find a vulnerability for it and they are doing a good job. Going with PHP5 we would have to patch the servers monthly just to keep up with the security vulnerabilities. Check their release notes and securityfocus. As for MySQL 5 I am hearing that it isn't getting great benchmarks and some of the new functions make it horribly slow. Just cause you can make a program do something... doesn't mean you should. Speed is essential in any RDBMS.

DirectAdmin Support said:
Adding options is probably the easiest way to go about it. Although making everything more complex, in the end will probably make everyone happier.
Click to expand...

I love the conf file idea. Great way of simplifying install options.

Big Wil
 
Chrysalis, I said you many times, that it's impossible with current custombuild script (I know you will say it's possible). You can use customapache if you don't like custombuild, custombuild is not installed by default, and you will be able to choose if you want it or not at the install time of DirectAdmin. About installation on the new server - I didn't get any bug-report from you, so I'm unable to reproduce the error. I appreciate your posts, and sorry if my post isn't very friendly, but it's really taking my time to repeat the same words few times to the same person. Why it's not possible? I think that I told you that, but I'll repeat:
1. CustomBuild replaces these lines in httpd.conf file, when you install PHP (if you don't have them, it won't work properly):
Code: 
#LoadModule php4_module /usr/lib/apache/libphp4.so
#LoadModule php5_module /usr/lib/apache/libphp5.so
#LoadModule suphp_module /usr/lib/apache/mod_suphp.so
2. CustomBuild uses extra/httpd-php-handlers.conf to write PHP handlers to the file, if the file isn't included into httpd.conf file - CustomBuild won't work properly.
3. CustomBuild uses extra/httpd-suphp.conf to write PHP-cgi info to the file, if the file isn't included into httpd.conf file - CustomBuild won't work properly.
3. CustomBuild changes the virtualhosts file (CustomApache has all the include lines in the main httpd.conf file), if you don't have directadmin-vhosts.conf file included into the main httpd.conf file - CustomBuild won't work properly.
4. CustomBuild uses extra/httpd-ssl.conf for SSL environment - if you won't have it included into the main httpd.conf file - CustomBuild won't work properly.
5. CustomBuild uses extra/httpd-vhosts.conf file for IP/hostname (/var/www/html), if you won't have it included into the main httpd.conf file - CustomBuild won't work properly.
6. There are some files that are needed for alias etc., and they won't work properly with old configs too.

So, as I said - it's better to use customapache, if you don't want to change the /etc/httpd/conf structure. Sorry again, if this post isn't very friendly.. Have a good day.
 
Martynas, I understand your reply, and I understand Chrysalis's original post.

What I don't know (hopefully you can tell me) is whether or not there's a warning when the conversion is done that you may have to import any custom changes from your old httpd.conf file to the new one, and is the old one saved?

As long as both above are true, then I don't see a problem, though if a lot of folk are going to convert then perhaps one of us (not me ;) ) can create a little script using some intelligent diffing and patching to automate it.

Jeff
 
DirectAdmin Support said:
I've been doing:
Code: 
ln -s ../libmysqlclient.so /usr/lib64/mysql/libmysqlclient.so
Because there is a 64-bit version in /usr/lib64/libmysqlclient.so.
Click to expand...
Thanks for all your good work, John. Can the link be added by the DirectAdmin install when the DA install is done?

Martynas, can the link be added automatically somewhere when the conversion to CustomBuild is done? (on 64-bit operating systems)?

Jeff
 
Configuration files are saved, but there is no warning about it.. Where that should be added?
 
You must log in or register to reply here.
Back
Top