Different include for apache non-SSL/SSL to avoid conflics

  • Hi,

    In my particular case, I need to add WSGI settings for my django projects where conflics since the includes reads twice the WSGI entry ("Name duplicates previous WSGI daemon definition"). So, why not have a

    Include /etc/apache2/imscp/mysite.conf and a Include /etc/apache2/imscp/digikits.com.ar_ssl.conf option? (to not mess with the automated generated main conf).

    I know this is duplicate post of Different Apache confs for SSL/non-SSL but I didn't saw an answer there.


    Edited once, last by GuS ().

  • theemstra

    Added the Label to be discussed
  • Hi, thanks for reply and happy new year!

    Specific because of using Python/wsgi/django?

    As far as I can see this is outside the scope of the i-MSCP project, but I think it would be possible to implement (or make it possible to implement) with a listener. Let's await the reply of Nuxwin in this case.

  • Good evening,

    Having dedicated included file for both http and https could do the job but this would break older sites which repose on single included file. So, I"ll not implement that in core. However, you can always override default include statement using a listener file.