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

[blackbumer]

Originally Posted by 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?

we are waiting files from you and ready to test it

[till]

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

As far as I know you changed also ptahs e.g. for satistics. This will mess up everything on update.

The only otion that I see at the moment for an inclusion is to rewrite your addons so that it follows the ispconfig paths and databse field names.

I'am sorry but I really can not include a piece of software even in a next major release that will break thousands of exsiting server installations.

Nevertehless I will review your code and see If it can be made compatible with the released ispconfig versions as it will be less work to chnage your plugin then to cahnge the whole ispconfig code to make it compatible with your plugin.

[Keeper]

This topic is very interesting and I'm glad there is progress in getting nginx support to ISPC3. However, when this gets finalized I hope it does not require php-fpm. php-fpm still requires modifying PHP source manually, which means automatic security updates won't work.

[eugenesan]

Actually there is a project that should allow php-fpm as addon to PHP.
http://php-fpm.org/Main_Page

Unfortunately progress is almost stopped, since I am very busy lately.
If someone willing create/rebase patches based on older version, I am ready to release the code.

[Ovidiu]

whats the status with this plugin?

[omega13a]

Originally Posted by eugenesan

My intention was eliminate mail server usage (thanks to gmail) and totally replace apache+libphp with nginx+php-fcgi-fpm and not to add nginx as reverse proxy.

Question about the php-fpm part, would we be able to have php-fpm run as a different user for each website because I have php-fpm already set up like that and I don't want to have all the php-fpm processes running as the same user.

[eugenesan]

About a month ago I've started porting my old patches to latest ISPConfig.
Focus was:
1) Add support of PHP 5.3 in FPM mode. (with PHP-FPM sites of each user runs under their own user and PHP instances number grows dynamically on demand)
2) Update support for Nginx.
3) Refresh support for external mail (GoogleApps) using msmtp.
4) Add support for above in installer, as so called "lite" mode.

Currently code is partially written but still not tested due to time constrains.
I've posted one of the snapshots (Not the latest snapshot) here: http://gitorious.org/ispconfig-lite

Hope to to find some time to finish that soon.
Critics, comments and ideas are welcome.

[hopoo]

This is my short Tip of traffic analysis.
debian + Nginx + vlogger + ispconfig3.0.3

]# vi /etc/nginx/conf.d/ispconfig.conf
log_format combined_ispconfig '$server_name $remote_addr - $remote_user [$time_local] '
'"$request" $status $bytes_sent '
'"$http_referer" "$http_user_agent"';
access_log /var/log/nginx/vhost.access.log combined_ispconfig;

]# vi /root/bin/my_nginx_log_analysis.sh
#!/bin/sh

VHOST_LOG_FILE=/var/log/nginx/vhost.access.log
LOG_DIR=/var/log/ispconfig/httpd

/usr/bin/tail -f $VHOST_LOG_FILE | /usr/local/ispconfig/server/scripts/vlogger -s access.log -f 300 -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" $LOG_DIR

]# vi /etc/logrotate.d/nginx
/var/log/nginx/*.log {
daily
missingok
rotate 52
compress
delaycompress
notifempty
create 640 root adm
sharedscripts
prerotate
/usr/bin/killall tail
endscript
postrotate
[ ! -f /var/run/nginx.pid ] || kill -USR1 `cat /var/run/nginx.pid`
/usr/bin/nohup /root/bin/my_nginx_log_analysis.sh&
endscript
}

Waiting for feedbacks.

[Undo]

Hi folks,

What's up with this "plugin", or "patch", or any name you would give to this wonderful work ?

I'd like to use it & take part in its development but the code posted on gitorious is just too old and the commit tree too messy (only 3 commits for hundreds of files modified).

Waiting for news for Eungenesan

[Undo]

Originally Posted by hopoo

This is my short Tip of traffic analysis.
debian + Nginx + vlogger + ispconfig3.0.3

]# vi /etc/nginx/conf.d/ispconfig.conf
log_format combined_ispconfig '$server_name $remote_addr - $remote_user [$time_local] '
'"$request" $status $bytes_sent '
'"$http_referer" "$http_user_agent"';
access_log /var/log/nginx/vhost.access.log combined_ispconfig;

]# vi /root/bin/my_nginx_log_analysis.sh
#!/bin/sh

VHOST_LOG_FILE=/var/log/nginx/vhost.access.log
LOG_DIR=/var/log/ispconfig/httpd

/usr/bin/tail -f $VHOST_LOG_FILE | /usr/local/ispconfig/server/scripts/vlogger -s access.log -f 300 -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" $LOG_DIR

]# vi /etc/logrotate.d/nginx
/var/log/nginx/*.log {
daily
missingok
rotate 52
compress
delaycompress
notifempty
create 640 root adm
sharedscripts
prerotate
/usr/bin/killall tail
endscript
postrotate
[ ! -f /var/run/nginx.pid ] || kill -USR1 `cat /var/run/nginx.pid`
/usr/bin/nohup /root/bin/my_nginx_log_analysis.sh&
endscript
}

Waiting for feedbacks.

I see a problem with your way to handle it : what happens if the tail -f process is being killed for any reason ? Especially, what happens if you reboot your server in the middle of the day ? It will stop logging for half a day ...