Posting just to give some advice that a dumb slopbot won't. In addition, this advice should be easy to extend without the need to use a slopbot.
This is a "how long is a string question" but I think you may be feeling lost because you're not giving enough weight to previous suggestions (and/or ignoring/not understanding advice before establishing a stable baseline from which to grow). After a quick read of this thread, it seems like "(basic) version control + make" has been mentioned a few times. I think you should at least *try* to copy/create a system admin file (like pf.conf) to a directory and create a makefile to install it and ask questions (or identify areas to improve upon) from there. -i.e. not just ignore seemingly "good advice" from seemingly "experienced users". Here is how *I* would start to tackle this problem if I were in the OPs shoes (-i.e. how I would evaluate if that was 'good advice' or not for my needs).
Initial plan (example): bury something deep enough to give it an understandable context and plan to snapshot/backup that directory:
An imagined directories/files that seem to be self-explanatory could be something like:
Code:
/opt/conf/sys/system_admin
and/or
/opt/conf/sys/user_admin
and/or
/var/db/repositories.git
/var/db/repositories.fsl
/var/db/repositories.rcs
/var/db/whatever...
The following (below) is about as complex a makefile--to install "pf.conf" to /etc/--one would need to be (use which ever system/user config file you want. I just choose pf.conf as an example).
Use: copy/create pf.conf into a directory, do version control (*not* behind https, or at most ssh(1)!), edit pf.conf, type `make` and your done.
I think you're also risking asking/answering the wrong questions initially. For example, Ansible (for example): someone says they use ansible. Do not automatically assume this is a panacea for you as well, they probably use it themselves because they use it professionally or have taken the time to learn it or have a need (will adopting this "thing" incur more/acceptable overhead/learning/management for you?). Do *you* need ansible (maybe/maybe not). -e.g., if you need remote management, what's wrong with a (for as long as it's still around) scp(1), or a tar(1) pipe via ssh(1), or even just the -t switch for ssh(1) (these are as close as you can get to zero dependency, will not break on an update [well, scp(1) will eventually], and easy to understand). ...Start simple, and when that breaks or isn't good enough, change direction and/or ask questions.
Code:
#===---------------------------------------------*- makefile -*---===
#: system_admin
# This makefile will install the things I care about.
#===--------------------------------------------------------------===
CP := cp
pf:
PF_CONF='/etc/pf.conf'
@$(CP) pf.conf /etc/pf.conf
PF_RESTART='Restarting PF...'
service pf status
service pf restart
another:
ANOTHER='/someplace/elese'
@$(CP) ....
.PHONY: all
all: pf another
Add some tables to your pf.conf mgmt setup.
Make some updates and see if you (don't) like the system.
If you have several nodes see if you can push from a single-source with what you know/understand now (there will always be people around to tell you are doing it wrong and suggest a different method).
Worth mentioning that part of my point is that you should not always incur extra (possibly unnecessary) overhead for yourself just because someone/something on the internet told you it's the way the cool kids do it (think for yourself).
////