New build system (BETA)

Thanks, John. I still see reports of problems in this thread almost every day; support for DA will be a nightmare if it's made live before everything is fixed.

Jeff
 
jlasman, just a minor bugs ;) Like updating not from beta folder (because it wouldn't be in beta) or users haven't updated DirectAdmin to the latest version and don't have the new templates... There are no plans about support for DA till the other month (release of DA).
 
I tried to upgrade php to 5.5.2 with: ./build php
but when php was built and I restarted apache no php page could been shown, instead I got php source from apache.
I have apache 2.2.4 and php 5.2.1 with suphp, and 4.4.6 as cli.
How the upgrade procedure should be made?
 
ScOuT, do you use the latest version? If yes - you must switch to the new configs of apache (if it hasn't been done yet). And check your options.conf if everything is okay here.
 
How do I check configs for apache?

I installed apache 2.2.4 and suphp in april using current version (in that time) of custombuild and it went OK. Before upgrade (today) I did "./build update" and got latest version of custombuild script before upgrade to PHP 5.2.2
 
That's because you did ./build update, and not ./build update_script :) In this way options.conf gets owerwritten. Do "./build all d" now :)
 
Since this is a VPS machine, I restored everything from a backup I made before upgrade, and now I did ./build update_script and will try to upgrade tonight again. Do I need to make "./build all d" or just "./build php y"

Thnx smtalk.
 
After upgrading with this custombuild script, I have a question about the httpd.conf.
It looks very clean now, but I'm missing optimizations like:

StartServers
MinSpareServers
MaxSpareServers
ServerLimit
MaxClients
MaxRequestsPerChild
etc..

Shouldn't these settings be present in httpd.conf?
Will they still work for apache 2.2.4
 
I believe what you are looking for is in the 'extra' directory: /etc/httpd/conf/extra

And the specific file is 'httpd-mpm.conf'

Grant
 
I just tried to update PHP to 5.2.3, and did:

./build update_script
./build update_data
./build all d

It went fine, but no PHP script gets executed, I get source of all .php files.

OS is CentOS 4.4 64bit.
What could be wrong?

Options.conf was set to PHP5 - cgi, PHP4 - cli, default PHP5, apache2.
 
Try to restart httpd. If it doesn't help - please contact me and I'll take a look at it for free.
 
Sc0uT said:
I just tried to update PHP to 5.2.3, and did:

./build update_script
./build update_data
./build all d

It went fine, but no PHP script gets executed, I get source of all .php files.

OS is CentOS 4.4 64bit.
What could be wrong?

Options.conf was set to PHP5 - cgi, PHP4 - cli, default PHP5, apache2.
Click to expand...


same here, one big mess.
 
smtalk said:
May I see your server?
Click to expand...

l already managed my config,

what i noticed where mod_suphp.c and mod_suphp.so one is for apache 1.3 and the other for 2.x.

The templates contains mod_suphp.c, but if i running 2.x the templates are useless. Also the .so libs for php wont be created.

My mistake was, first compile apache 2.2 , going back to 2.0 with custom build is a no-go.
 
jlasman said:
Thanks, John. I still see reports of problems in this thread almost every day; support for DA will be a nightmare if it's made live before everything is fixed.

Jeff
Click to expand...

I think I have to stand with Jeff as a skeptic on this build. There are far too many issues that this new build is going to have on us. I understand the need to upgrade to bigger and better things but issues like Apache 2 not having mod_frontpage and suPHP not allowing .htaccess files sort of stands in our way. Many customers use .htaccess files for things like DENY purposes and such, which suPHP doesn't have a replacement for to my knowledge.

Before starting this new custombuild project did anybody ask the DA license holders what they need out of the new build script? Was there a poll that I missed?

In short I need Apache 2, PHP4, suPHP with Mod_Frontpage and the abilility to expand to PHP5 in the future once the security for the product is stable.

Mod_Frontpage needs to stick around no matter what. There are still millions of customers that have Frontpage and will continue to use Frontpage no matter what Microsoft says. Those customers are my potential customers. I own a 1979 Chevy Berlinetta that is a sort of weekend project for me. They still make tires and fuel for it. ;-)

I would suggest a few working additions to the conf file like:

ap1_frontpage= yes/no
ap2_frontpage= yes/no
ap1_modperl= yes/no
ap2_modperl= yes/no
mysql_ver=4/5

I think you can tell where I am going with these. Once these options are available I can start considering the project. Until then I think DA needs to keep in mind that this build doesn't necessarily reflect the desires of all of its users.

Any other senior DA users want to point out things like I have? I think it is a good idea since it is a beta project in need of a few revisions. Silence will not feed the project. Mother taught me that a closed mouth don't get fed.

Big Wil
 
You must log in or register to reply here.
Back
Top