I want to upload some parts of /etc/ towards gitlab. [Not the private keys]

In what way is this proposal different from (or better than) simply create a tar file of the current configuration in /etc/ regularly, then storing those tar files somewhere? What does using git (or a similar source control system) give you?

Here are a few suggestions of why git (or any other source control system) might be better, but I don't think you're planning to use them: If changes are made by different people (many engineers working on it), you can track who did what, and see the history of changes. If multiple people or tasks are doing simultaneous changes, you can work on branches, and merge/integrate them. You can integrate the source control with a testing system, and automatically verify that the product is "good", but for the /etc/ files used for a system install, that's difficult (how do you define "good", how do you implement unit and system tests).

Why do you want to store the data on gitlab? Why not upload the data (either as tar files or as a directory of small files) to an arbitrary storage service, which could be local (a USB stick) or in the cloud?
 
The suggestion of putting /etc files on githup sounds like suggesting to air ones undies on time square. IMHO it is a bad idea and asking for trouble.
 
Good joke your magesty. You are wright you must be careful. To problem is that innocent and dangerous files sit in /etc & /usr/local/etc.
They are not split up. I think i found private keys in /usr/local/etc.
Following your advice i changed /etc & /usr/local/etc repository to visibility private, in order to not attract attention.
 
Sire, ye need to be careful with the keys to thee castle! That is all this humble jester suggests, because, you heard what they did to the Doge?
 
Alain De Vos said:
I think privacy is of great importance. So when gitlab asked me my personal language i entered LATIN.
Thing is i cannot read LATIN.
Click to expand...
Then why are you using gitlab.com in the first place instead of hosting a gitlab yourself?

Also, you probably don't actually need all that software. A git repo accessible with via ssh key is enough to handle code versioning. Even more so when it's just some conf files.
 
If my disk dies, the git-server on the disk dies with it.
But it's indeed an interesting idea, when i put the storage on my external disk.
 
Alain De Vos said:
If my disk dies, the git-server on the disk dies with it.
But it's indeed an interesting idea, when i put the storage on my external disk.
Click to expand...
So use a small RAID setup; even 2-3 disks mirrored (or small partitions from 2-3 disks) have adequate reliability for a small data set at amateur expectations.

Or use a single small disk, and then use a random cloud service for backups. For example, once a day make a tar ball of your git repository, compress and encrypt it, and upload it to the cloud storage service you favor. That's much more secure than putting it on gitlab. In case of a failure of your disk, you might lose up to 1 day of updates; that should be tolerable.
 
You must log in or register to reply here.
Back
Top