[Spacewalk-list] Spacewalk as Virtual Host?

Tue Mar 8 07:41:16 UTC 2016

I have a couple of test servers where I am sharing the httpd server by setting ip address for the ”other” services.

So each server has 2 ip addresses,
the spacewalk confs are named zz-etc so they will be read after all the others,
I then change the “others” from *:80, *.443 to for example 1.1.1.2:80 and 1.1.1.2:443
I leave the spacewalk confs with *, and it seems to work, but I have not deployed this in our production environment, there is more testing to be done.

Yesterday for example I discovered an “other” service that expected to use 127..0.0.1 for example, but it was fixed by simply adding a VirtualHost line with 127.0.0.1:80, so far so good.

regards, and I hope I haven’t misunderstood your question.
…C

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Lachlan Musicman
Sent: den 7 mars 2016 06:10
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Spacewalk as Virtual Host?

Hi,
We have installed Spacewalk on a "utilities" server, and I would like to change Spacewalk to a virtualhost set up in Apache2 so we can serve a number of services through Apache2 (Icinga, etc).
The only advice I've found is an email from this list - but it's now 6 years old.

https://www.redhat.com/archives/spacewalk-list/2010-February/msg00206.html

Do people still recommend against it?
cheers
L.

------
The most dangerous phrase in the language is, "We've always done it this way."

- Grace Hopper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160308/5f25d38d/attachment.htm>