Re: best practices for configuring multiple VirtualHost Apache WWW servers in Fedora?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Sat, 2023-08-26 at 20:29 +0200, Franta Hanzlík via users wrote:
> I suppose I will create four configuration files for each Virtualhost 
> in the /etc/httpd/conf.d/ directory (eg srv1_intranet.mydom_ssl.conf, 
> srv2_intranet.mydom.conf, srv3_www.mydom_ssl.conf, srv4_www.mydom.conf).
> But how best to proceed?

That's generally how such things are done, one file in conf.d per

> IMO if I leave zoneminder/mrtg/apcupsd/geoip/roundcubemail as they are,
> in /etc/http/conf.d/, they will apply in all VirtualHost - which I
> don't want.

Are you sure?  You can always do some tests, mock up some examples and
see what happens.  

I've only got Squirrel Mail installed on my LAN as an extra through
Apache, and I can see that any virtual host domain with /webmail
tacked on the end of it goes into the local Squirrel Mail site (the
same one on each virtual host).

It'll depend how they're written.  If they're similarly constructed as
the virtual host configurations, they only apply to themselves.

You could put virtual host parameters into them.  You could shift them
out of conf.d and have a specific virtual host include them into
itself.  You could forbid the path within your virtual hosts.

> And if I put each one in its VirtualHost and delete the original in
> /etc/httpd/conf.d/, it reappears there when its RPM package will be
> updated.

Unfortunately that's down to how those packages are written.  

 * They may realise there's custom config files and leave yours alone
   adding some conf.rpmnew files for you to compare new against old and
   update your own conf files.
 * They may do nothing if there's an existing .conf file.
 * They may move your config files to conf.rpmold and implement their
   new conf files.
 * They may simply bulldoze through existing config files and replace

If you feel it's going to do something along the lines of the last two
things, you'd want to keep back-up files ready to reimplement after any

I've generally found that Apache's conf.d/conf files didn't get stomped
on by updates.

uname -rsvp
Linux 3.10.0-1160.95.1.el7.x86_64 #1 SMP Mon Jul 24 13:59:37 UTC 2023 x86_64
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux