Topic: httpd.conf - (copy old or edit new after upgrade)

[solorize]

Hi, hopefully this is an easy question.

Every time I upgrade Apache webserver I take a copy
of my current HTTP.CONF file, and then once the
updated version of Apache webserver has been installed.
I then go through and edit the new HTTP.CONF file
to replicate the code that I had in my previous file
(which has customised edits to the code, that I have made).

What I would like to know is; am a wasting my time doing
this, when I could just copy my current HTTP.CONF file
over the new one?

Or

Could the new HTTP.CONF file have additional / modified code
that the older version may not have? So would not be recommended
for me to do this and would always be best to just edit the new file
after and update, to avoid possible problems.

Thanks in advance

[mrdj1024]

keep the old one
those rarely change.

[DnvrSysEngr]

I second that. I keep my old Conf folder as it has everything just the way I want/need it. I may peruse the Conf folder that comes with the new build that I just downloaded, but 99.9% of the time there is nothing new / important / relevant in the Conf folders for my setup.

FWIW - Same holds true for NGinx conf files.

[James Blond]

I use git for tracking all my changes. So there are no backup copies flying around. And I can roll back if needed.

[solorize]

Thankyou both for confirming.

I will give it a go when I next update Apache.
Hopefully this will save me a bit of time
not having to edit the new one

[mrdj1024]

you can do the same for php updates aswell so you dont have to constantly configure the php.ini file everytime a new update is released.
if your using php 8.1 you can update everytime it updates by downloading the new php version,just make sure its in the same php branch,like 8.0 with 8.0 or 8.1 with 8.1 etc.
also make sure that if your using apache you get the thread safe php builds.
upgrading from php 8 to 8.1 wont work using this method.
it works only for php updates in the same "family"
just copy and paste and overwrite the files in your php folder with the new ones
same principle applies to mariadb/mysql versions in the same release family.

[tangent]

My strategy is to make minimal changes to the default httpd.conf file, by referencing an optional include file added at the end, e.g.