ISPConfig3 plugable mail subsystem (for Google Apps) and nginx as alternative

[eugenesan]

Ok, I'll have to prepare the patch first :-)
I'll update you with details soon.

[blackbumer]

Originally Posted by eugenesan

Hi all,

Here it comes, Nginx support for ISPC.

Basic support only:
1) No installation support
2) No automatic configuration of ISPC web.
3) No SSL support.
4) Currently only supports php-fpm as php fastcgi engine.
5) Tested and built on Debian based system, sorry rpm guys.

Few notes for maintainers:
*) I had to dos2unix few files so take it into account when diffing.
*) I've changed in some places hard coded references to apache by webserver.

To use:
*) Install php-fpm and mydns (google or contact me for patches for Debian based distros)
*) apply patch
*) install without web
*) configure ISPC in nginx by adding /etc/nginx/available-sites/ispconfig with next content:

# ISPConfig virtual host

server {
	listen   8080;
	server_name  _;

	access_log  /var/log/nginx/ispconfig.access.log;

	location / {
		root   /usr/local/ispconfig/interface/web/;
		index  index.php;
	}

	# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
	#
	location ~ \.php$ {
		fastcgi_pass   127.0.0.1:9000;
		fastcgi_index  index.php;
		fastcgi_param  SCRIPT_FILENAME  /usr/local/ispconfig/interface/web//$fastcgi_script_name;
		include /etc/nginx/fastcgi_params;
	}

	# deny access to .htaccess files, if Apache's document root
	# concurs with nginx's one
	#
	location ~ /\.ht {
		deny  all;
	}
}

make link to /etc/nginx/enabled-sites/ and restart nginx.
If I didn't forget something, ISPC should be operational.
*) Now enter ISPC web and go to system->edit server->select server->config. Here modify next:

[web]
website_path=/var/clients/client[client_id]/web[website_id]
website_symlinks=/var/www/[website_domain]/:/var/clients/client[client_id]/[website_domain]/
vhost_conf_dir=/etc/nginx/sites-available
vhost_conf_enabled_dir=/etc/nginx/sites-enabled

[global]
webserver=nginx

*) if brave and going to update existing DB perform next changes:

-  `apache_directives` text,
+  `webserver_directives` text,
+  `protected_folders` text,

Waiting for feedbacks.

is it right method of isntallation patch :

cd /usr/local/src/
svn checkout svn://svn.ispconfig.org/ispconfig3/trunk/
mv trunk ISPConfig-trunk
patch -p1 ../ispconfig-trunk.nginx-0.1.patch

should i apply all patches in this thread or just last one? (ispconfig-trunk.nginx-0.2.0.4)

[eugenesan]

Hi,

Only the latest patch should be applied, but I suspect there maybe a problem with last one. Seems like several files slipped into "original" tree before I've created patch.

At the moment I have running setup but can't find time to "rediff" it with latest version. In addition some functionality still not documented :-(

I can try to pack a tarball which can be used to merge with latest ISPC version.
What do you think?

[blackbumer]

it will be very nice !!!
very need it

[cubells]

I'm eager to test it!!

[eugenesan]

Hi,

At the moment I am "extracting" changes from local setup to installable tree.
I still need to prepare SQL template, that can take some time.
Hope to finish very soon, maybe tomorrow...

[till]

Few notes for maintainers:
*) I had to dos2unix few files so take it into account when diffing.

Normally all files should be with unix linebreaks. Do you know which filesw ere wrong?

*) I've changed in some places hard coded references to apache by webserver.

Thats sad as it breaks the compatibility with the existing ISPConfig 3 installations and will prevent that we add this patch to ispconfig main branch.

[eugenesan]

Originally Posted by till

Normally all files should be with unix linebreaks. Do you know which filesw ere wrong?

I didn't write down file names, but when I'll post a patch we probably will see it.

Originally Posted by till

Thats sad as it breaks the compatibility with the existing ISPConfig 3 installations and will prevent that we add this patch to ispconfig main branch.

Yes, I am aware of it, but as I recall that was the only rational solution.
Actually I am pretty sure everything will continue to work for Apache too.
And we can always assume Apache is the default.

[till]

Yes, I am aware of it, but as I recall that was the only rational solution.
Actually I am pretty sure everything will continue to work for Apache too.

That depends on what you changed. If you changed the name of a database field e.g. the apache_directives field to webserver_directives, all installations with your patch can not be updated with a normal ispconfig update in future and are not able to install any of the bugfixes or possible future security fixes. If they would install an update or use the ispconfig update function, they would loose the complete server configuration in the database as of the incompatible db scheme.

[eugenesan]

Yes, here you right.

But, for example, if next update will include updates to both DB fields and references in code, we may solve the problem.

In addition you may consider adding my changes to next major release.
That way people who wish to evaluate nginx will use trunk or will have to wait for final release.
In future, people willing to move to that release, from older ISPC, will be required to perform minor adaptation to their DB.

Unfortunately I don't recall all changes I've performed and after I'll review final patch I may reply with concrete examples.

What do you think about my proposal?