Use Fossil for system files?

As a new Fossil user , I am curious if there are any negative consequences when using Fossil to store things like / etc /, / usr / local / etc from Unix, such as FreeBSD and OpenBSD. If I do this for multiple systems, I think I created a branch with each host name to track these files.

  • Q1: Have you done it? Do you prefer a different VCS for processing system files?

  • Q2: There have been a lot of changes in Fossil in recent years, and I am curious if it is possible to limit who can combine the branches with the trunk. From reading previous threads this was not possible, but there are two ways:

    a) tell people not to merge with trunk

    b) a clone and an accompanying body take changes from their repo from people

+4
source share
1 answer

System configuration files stored in /etc, /varor /usr/local/etc, can usually only be edited by the root user. But since root has full access to the entire system, an erroneous command can have dire consequences.

, , , setup, git. , FreeBSD, . shared , . .

:

  • .
  • .
  • . , 1.
  • . .

script ( install) . .

, script, deploy, . , . .

+3

All Articles