LAMP is a popular open source web platform commonly used to run dynamic web sites and servers. It includes Linux, Apache, MySQL, and PHP/Python/Perl and is considered by many the platform of choice for development and deployment of high performance web applications which require a solid and reliable foundation.

This appliance includes all the standard features in TurnKey Core, and on top of that:
SSL support out of the box.
PHP, Python and Perl support for Apache2 and MySQL.
PHPMyAdmin administration frontend for MySQL (listening on port 12322 – uses SSL).
Postfix MTA (bound to localhost) to allow sending of email from web applications (e.g., password recovery)
Webmin modules for configuring Apache2, PHP, MySQL and Postfix.

A separate LAPP stack appliance features PostgreSQL instead of MySQL.

this program also available on our VPS images.

Incoming search terms:

edit:
/usr/local/lib/php.ini
Search for

; Maximum allowed size for uploaded files.
upload_max_filesize = 2M

Change the 2M to whatever new value you want, then restart apache.

Incoming search terms:

Pelanggan YTH

Hari ini, kami telah melakukan update untuk Litespeed web server yang digunakan pada hosting server kami yaitu vhost 03, vhost 04, vhost 05 dan vhost 06. Adapun kelebihan dari versi terbaru ini adalah :

Version              Release Date      Type
Web Server 4.0.10     08-18-2009     Minor bug fixes and Security enhancements

* Fixed 503 errors and can tolerant PHP crash under certain situation.
* Changed admin console to suEXEC mode, which is more secure and stricter on file permissions.
* Improved PHP build script in admin console.
* Fixed a bug that causes 403 access deny when access file containing symbolic link.
* Fixed a few minor Apache compatibility issues.

Incoming search terms:

If you have both suPHP and CLI installed on your system, but don’t feel like renaming all of your file.php to file.php4 (for example), there is another means to chose between php versions, without requiring to touch your php files.
To force php files to use CLI (on the assumption your default php version uses suPHP) create an .htaccess file in your public_html directory, with the following:

<FilesMatch "\.php$">
AddHandler application/x-httpd-php .php
</FilesMatch>

To force php files to use suPHP (on the assumption your default php version uses CLI) use the following:

<FilesMatch "\.php$">
AddHandler x-httpd-php5 .php
</FilesMatch>

This last one is on the assumption that php 5 is suPHP and CLI is php4. If php4 was suPHP, then you’d use x-httpd-php4 to force .php files to use suPHP with php 4.

Incoming search terms:

By default, suPhp is compiled in "paranoid" mode. This means that the settings in the user httpd.conf files:

suPHP_UserGroup username username

will require all php files to be owned by username or suPhp will throw a "500 Internal Server Error".
This does not apply to domains, when used normally, because each domain has it’s own VirtualHost with the suPHP_UserGroup inside it using the correct settings.
The ~username (UserDir) method will fail in paranoid mode, because there is not a virtualhost for each ~username path, and no suPHP_UserGroup settings for each user, hence you get the 500 error.
The solution to this is to compile suPhp in "owner" mode instead of "paranoid" mode.
To do that, run these commands.

cd /usr/local/directadmin/custombuild
mkdir -p custom/suphp
cp -fp configure/suphp/configure.suphp custom/suphp/configure.suphp
perl -pi -e ‘s/paranoid/owner/’ custom/suphp/configure.suphp
./build clean
./build suphp
cd /usr/local/directadmin/data/templates/custom
cp -f ../virtual_host* .
perl -pi -e ‘s/suPHP_UserGroup/#suPHP_UserGroup/’ virtual_host*.conf
perl -pi -e ‘s/suPHP_UserGroup/#suPHP_UserGroup/’ /etc/httpd/conf/httpd.conf
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue

Which will change all references of suPHP_UserGroup to #suPHP_UserGroup, basically, just commenting them out.

Incoming search terms: