[scl.org] Recommendations for enabling scl for httpd
Davis, Daniel (NIH/NLM) [C]
daniel.davis at nih.gov
Thu Oct 1 13:56:40 UTC 2015
We've decided not to run httpd24 because we a choice to build mod_wsgi for standard httpd, or to build mod_auth_cas, mod_jk, and some others for httpd24. EPEL contains the build of mod_auth_cas, and we already have mod_jk. So, basically, the ecosystem for standard httpd is better.
We also think that system admins and some dev ops folks will look first in /etc/httpd/conf/httpd.conf for the configuration, and so it is a minor advantage to stick what has been standard in the RedHat world.
I'll keep the service environment file in mind as we move forward into softwarecollections gains more module support. Here in security focused government, we like software collections more than Docker, on the whole. Docker is cool, but Nessus can theoretically scan softwarecollections better.
From: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] On Behalf Of Jan Kaluža
Sent: Thursday, October 01, 2015 3:00 AM
To: sclorg at redhat.com
Subject: Re: [scl.org] Recommendations for enabling scl for httpd
On 09/29/2015 10:55 PM, Davis, Daniel (NIH/NLM) [C] wrote:
> What is the best practice for enabling rh-python34 during the process
> of starting Apache httpd as a service?
You can add it into /opt/rh/httpd24/service-environment file and httpd24 should automatically enable that service when started using systemd or initscript.
> Would it be good to add the following to /etc/sysconfi/httpd:
> if [-f /opt/rh/rh-python34/enable ]; then
> . /opt/rh/rh-python34/enable
> Dan Davis, Systems/Applications Architect (Contractor),
> Office of Computer and Communications Systems,
> National Library of Medicine, NIH
> SCLorg mailing list
> SCLorg at redhat.com
SCLorg mailing list
SCLorg at redhat.com
More information about the SCLorg