Vesta Control Panel - Forum

After stripping and symlinking some binaries in nginx/sbin, php/bin and php/sbin my /usr/local/vesta size went from 128Mb to 37Mb which, to me, is still too large for a few 1000 docker containers but certainly better than what it was by default.

On ubuntu the end of the standard apache2.conf files has...

Include conf.d/
# Include the virtual host configurations:
#Include sites-enabled/

so have a look at...

/etc/apache2/conf.d/vesta.conf

and you will find it includes yet another conf file in a users home dir, ie; for me it is...

/home ...

I hope this is the right section to post about this low priority issue. I was wondering why a du of /usr/local/vesta was so large and noticed the 2 binaries in /usr/local/vesta/php/sbin were not stripped and both binaries were exactly the same size so I stripped them and symlinked one to the other ...

I could not figure out why my apache2.conf and nginx.conf were not being generated so after many hours of trying to figure out how VestaCP creates those files I finally noticed a sed error when /forward/slash paths were being used so I did a wholesale replacement of / to # and now my config files ...

I am also very interested in running only nginx and php-fpm and wondering how I can stay in touch with the most recent development for the next release? Perhaps I can help out as I've been using ISPConfig on a few servers and it uses nginx + php-fpm with unix:sockets.