• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Prevent Plesk from creating not used webserver configs

ChristophRo

Regular Pleskian
Is it possible to customize the Plesk templates, so it does not create the webserver and webmail configuration files at all?
Per default it creates a full apache2 config file, even if apache2 is not used. (nginx proxy mode off)
It does also create nginx and apache2 webmail config files, even if webmail is disabled.

I'm asking this, cause I'm looking for a way to optimize and speed up the configuration re-creating and service load time on a system with almost 2k domains.


FYI: server is running Debian9/Plesk17.8
 
if you look at the webmail configs for domains that do not have webmail activated you will see that they are just comments: I don't think there will be much impact on the loading of the nginx/Apache services! ;)

As far as regards Apache config files for domains directly served by nginx... they will never be hit, so there will be no performance gain by not creating them.

At most you can spare some hundreds of KB of disk space (for 2K domains), but I don't think there will be any performance improvement.
 
Back
Top