Peter Van Lone a écrit :

do manual changes to the conf files get over-written at all by YAST and/or updates when they are installed?

certainly not is done correctly (in /etc/apache2/virtual.d/xxx.conf

It seems to me that this YAST gui is almost useless ... does anybody actually use it other than to initially enable the service?

it's probably not usefull. However, the example given (in the virtual.d folder) are a little too short. thanksfully the apache doc is quite good jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Peter Van Lone wrote:

unfortunately the apache docs are not suse specific ... and suse puts files and folders in different locations for different purposes than the plain apache does -- or at least I believe that is true.

Is there somewhere a document that describes well for RH users, how apache and php and mysql on SLES/SUSE are managed/deployed differently?

It's not really very difficult, Peter. /etc/apache2/httpd.conf has a very good explanation of what goes where and why. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ricardo Dias Marques a écrit :

I may be wrong, but I think that you mean /etc/apache2/vhosts.d (and NOT /etc/apache2/virtual.d/ ).

yes, you are right, all this virtuality... :-)) and is you define a virtual host, you have to set all here. For a limited number of virtual hosts, I think it's better to keep them all in the same file (and copy/paste the config) jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Aug 4, 2008 at 10:41 PM, David C. Rankin wrote:

There are two different types of virtual hosting:

(1) Name based virtual hosts; and (2) IP based virtual hosts.

You want to do IP based virtual hosts. The manual has good examples for setting up both. Both involve configuring the "virtual hosts" in a local config file. I use /etc/apache2/httpd.conf.local for the primary host definition.

yes I know about using the conf files to setup IP virtual hosts ... but I wanted to be able to do it from the YAST tool .. I guess it is too limited to do that, too bad. WHile we are talking about this, why do you use "etc/apache2/httpd.conf.local"? That sounds like a very SUSE specific thing (I don't remember ever seeing reference to that file in the apache docs? Does etc/apache2/httpd.conf get over-written by YAST, is that why you use the .local varient?

The only thing I use /etc/apache2/vhosts.d for is to define the vhosts-ssl.conf information for the server.

see this too was confusing to me ... is this standard apache stuff, or is this SUSE specific? Why is there a seperate directory for ssl.conf ... it looked from the apache docs if I remember that you could just do the ssl stuff in httpd.conf?

http://httpd.apache.org/docs/2.2/vhosts/

Will get you started. I use name based hosting. Otherwise, I'd post a config that would help.

thnx for the offer ... and thnx for taking the time to reply! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, Aug 5, 2008 at 7:23 AM, David C. Rankin wrote:

O -- Sorry about that. I never use Yast for any serious package setup. I have found that none of the package documentation (i.e. Apache manual) gives configuration in Yast instruction. I have always wondered why people don't mind spending hours figuring out how to make a configuration work in yast when in the same amount of time, the complete configuration could have been learned without the limitations imposed by yast.

Yast is good, but remember it is only "Yet Another Setup Tool".

yes, yes ... but the most important of the questions I asked were WHY use the .local version of httpd.conf? I don't think the generic apache docs ever mention such a beast ... is this SUSE specific, and what is the purpose of using it instead of the straight httpd.conf file? Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Peter Van Lone wrote:

On Tue, Aug 5, 2008 at 7:23 AM, David C. Rankin wrote:

...

O -- Sorry about that. I never use Yast for any serious package setup. I have found that none of the package documentation (i.e. Apache manual) gives configuration in Yast instruction. I have always wondered why people don't mind spending hours figuring out how to make a configuration work in yast when in the same amount of time, the complete configuration could have been learned without the limitations imposed by yast.

Yast is good, but remember it is only "Yet Another Setup Tool".

yes, yes ... but the most important of the questions I asked were WHY use the .local version of httpd.conf?

I don't think the generic apache docs ever mention such a beast ... is this SUSE specific, and what is the purpose of using it instead of the straight httpd.conf file?

Peter

The name choice is simply to help me remember that my local specific config is in the .local file. Also, when doing package updates, the httpd.conf can be overwritten with an update whereas the .local file will not be touched. I could have called it: my.feeble.attempt.at.httpd.conf and as long as I modified /etc/sysconfig/apache2 to read: APACHE_CONF_INCLUDE_FILES="my.feeble.attempt.at.httpd.conf" instead of APACHE_CONF_INCLUDE_FILES="httpd.conf.local" it wouldn't make any difference. The key is simply remember to tell apache what additional files to include. All and all, apache2 and the way suse splits the config files into different files that each deal with a specific part of the config has made it easier for me to learn than scrolling through a 400 line all-in-one config file. The individual files basically track to different manual sections. Mandrake used to simply use a single httpd.conf (7.0 days) and that was fine, but inconvenient. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan wrote:

* David C. Rankin [08-05-08 22:52]:

...

The name choice is simply to help me remember that my local specific config is in the .local file. Also, when doing package updates, the httpd.conf can be overwritten with an update whereas the .local file will not be touched. I could have called it:

my.feeble.attempt.at.httpd.conf

and as long as I modified /etc/sysconfig/apache2 to read:

APACHE_CONF_INCLUDE_FILES="my.feeble.attempt.at.httpd.conf"

instead of

APACHE_CONF_INCLUDE_FILES="httpd.conf.local"

it wouldn't make any difference. The key is simply remember to tell apache what additional files to include.

BUT, if you did not use "httpd.conf.local", when an update modified httpd.conf, the reference to your chosen config file would be missing. So there *is* a reason to use "httpd.conf.local".

Are you sure? I thought once you changed the sysconfig file from default to include anything else, it was flagged as don't update by package management? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, Aug 7, 2008 at 10:34 AM, Patrick Shanahan wrote:

* David C. Rankin [08-07-08 03:35]:

...

Patrick Shanahan wrote:

...

BUT, if you did not use "httpd.conf.local", when an update modified httpd.conf, the reference to your chosen config file would be missing. So there *is* a reason to use "httpd.conf.local".

Are you sure? I thought once you changed the sysconfig file from default to include anything else, it was flagged as don't update by package management?

You may be correct. I may be confusing the use of other *.conf.local files such as: /etc/modprobe.conf.local /etc/fail2ban/action.d/mail.conf.local among others

this is exactly what I was wanting to know ... and, now, I still am not sure whether I know it. Is it important that I tell the devs to use the .local variant of the conf files, or not? I just am not that familiar with configuring apache generally, and I certainly do not know enough either about the SUSE or the RH implementation to be able to explain what the devs will experience as a difference. Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org