Feature requests for CustomBuild

I was going to suggest support for php4, php5 and php6 in one script. Now it's 2 seperate scripts custombuild.1 (php4 & php5) & custombuild.2 (php5 & php6). Would be nice to built just 1 script for all php versions.

:)
 
1. PHP4 is EOL.
2. There would be too many options then.. (and too many checks). We already have 7 options with PHP5 and PHP6, so together with PHP4 we would have 23.

In my opinion it's not needed, if you think that it is - you can create a poll for that :) There is another poll about PHP4: http://directadmin.com/forum/showthread.php?t=28176
 
I've got another important update for custombuild:
I made changes to the directadmin/data/users/admin/httpd.conf script and everytime I rebuild apache I have to copy my old httpd.conf script in order for my websites to fully work again.


Would be great if custombuild could leave the script or would have an option not to rebuild the httpd.conf in /usr/local/directadmin/data/users/admin

:D
 
I would like to have multicore make support (-j2 or -j4 option to make for 2 or 4 cores). This would compile Apache and PHP much faster, which would decrease downtime when upgrading Apache from 1.3 to 2.0/2.2, which also requires a PHP recompile.

If this is already possible, please let me know :D
 
+3 mod_mono

php
under FastCGI
suhosin
xcache or eAccelerator​

apache
mod_evasive
mod_security
mod_qos​
 
Last edited:
I am not really sure if this is a custombuild thing or not. When I install DA I of course download the setup.sh script. When I run that I get a asked a bunch of questions. I found I could eliminate all teh question and just specify the answers on the command line. It makes getting started with the install a lot faster.

The method above used customapache. But now I want to start using custombuild. Is there anyway to specify all the options on the command line like above but use custombuild instead.

I have to install DA many times a month and its helpful to be able to just copy and paste the command to do this and simply edit the LID and the hostname.
 
Hi Floyd,

You can use custombuild with the command line options by typing:
Code: 
echo 1.1 > /root/.custombuild
before running the setup.sh. This will use all of the default custombuild options.

One step further than that, if you want custom options for custombuild, then you simply create the options.conf with the info how you want it, before running the seutp.sh (in addition to adding the above /root/.custombuild file)

Related from a while back (it's not beta anymore)
http://www.directadmin.com/features.php?id=774

John
 
On FreeBSD proftpd is being installed at /usr/sbin/proftpd when built with custombuild. However, during installation of DirectAdmin it gets installed at /usr/local/sbin/proftpd. This is also the path in the init script.

So either custombuild should:
1) Install proftpd in /usr/local/sbin/proftpd, or;
2) Modify the init script to start /usr/sbin/proftpd

Option one would be the better option, since all apps are being installed in /usr/local/
 
If DirectAdmin was integrated with CSF/LFD, then it would only work with Linux; FreeBSD doesn't work with CSF/LFD; it's a Linux-based firewall. For more information, look here.

Jeff
 
csf run with cpanel can catch mod_security hits and block accordingly. Something like this is what I meant, not that DA should be altered, more that mod_security installed on linux boxes has the option to work in a similar way.
 
It would be good for us running the services installed from ports in freebsd (or any linux) to have a way to see DA's last conf files.
I 've updated not using custombuild the dovecot service from 1.1 to 1.2
The conf files are different and i cant find a way to see the dovecot.conf file that i would got i updated via custombuild.

It wood by nice to add a ./build download_conf or something to have the latest conf files that da uses.
 
You must log in or register to reply here.
Back
Top