Shulou(Shulou.com)06/01 Report--

Editor to share with you what are the Git skills of managing the home directory in linux, I believe most people do not know much about it, so share this article for your reference. I hope you will gain a lot after reading this article. Let's learn about it together.

1. Text and binary position

Home directory

When managed by Git, your home directory is "no man's land" for everything except configuration files. This means that when you open the home directory, you can't see anything but a list of predictable directories. There should be no messy photos or LibreOffice documents, and there should be no temporary "I'll leave it here for a minute" temporary file.

The reason is simple: when you use the Git administrator directory, all uncommitted content in the home directory turns into noise. Every time you execute git status, you must flip over any files that were not tracked by Git, so it is important to save these files in subdirectories (add to the .gitignore file).

Many Linux distributions provide a set of default directories:

Documents

Downloads

Music

Photos

Templates

Videos

You can create more if you need to. For example, I distinguish between the music I create (Music) and the music I buy to listen to (Albums). Similarly, my Cinema directory contains other people's movies, while the Videos directory contains the video files I need to edit. In other words, my default directory structure is more detailed than the default settings provided by most Linux distributions, but I think it's good to do so. If there is no directory structure that suits you, you will store it in your home directory, because there is no better storage location, so please consider and plan a working directory that suits you in advance. You can always add more in the future, but you'd better get good at it first.

2. Set the best .gitignore

After cleaning up the home directory, you can instantiate it as an Git repository as usual:

$cd$ git init.

There is nothing in your Git repository yet, and everything in your home directory is not tracked. Your first job is to filter the list of untracked files and determine which files remain untracked. To view untracked files:

$git status .AndroidStudio3.2 / .FBReader / .ICEauthority .Xauthority .Xdefaults .Android / .arduino15 / .ash _ history [...]

Depending on how long you have been using the home directory, this list may be long. The simple thing is the directory you identified in the previous step. By adding them to a hidden file called .gitignore, you tell Git to stop listing them as untracked files and never trace them:

$\ ls-lg | grep ^ d | awk'{print $8}'> > ~ / .gitignore

When finished, browse to the remaining untracked files shown in git status and determine if there are any other files that need to be excluded. This process helped me find several stale configuration files and directories that I eventually discarded, as well as some computer-specific files and directories. I am very strict here because many configuration files perform better when automatically generated. For example, I never submit my KDE configuration file because many files contain information such as the latest documents and other elements that don't exist on other machines.

I keep track of my personalized profiles, scripts and utilities, profiles and Bash configurations, as well as spreadsheets and other text snippets that I often reference. If there are files that the software is primarily responsible for maintaining, ignore them. When I'm uncertain about a file, I ignore it. You can always cancel to ignore it later (by removing it from the .gitignore file).

3. Know your data

I use KDE, so I use the open source scanner Filelight to get an overview of my data. Filelight provides you with a chart that allows you to view the size of each directory. You can browse each directory to see what takes up space, and then go back and investigate other places. This is a fascinating view of the system that allows you to look at your files in a whole new way.

Filelight

Use Filelight or similar utilities to find unexpected data caches that do not need to be committed. For example, the KDE file indexer (Baloo) generates a lot of data specific to its host, and I definitely don't want to transfer it to another computer.

4. Don't ignore your .gitignore file

In some projects, I tell Git to ignore my .gitignore file because sometimes what I ignore is specific to my working directory, and I don't think other developers on the same project need me to tell them what the .gitignore file should look like. Because my home directory is for my use only, I will not ignore the .gitignore file of my home directory. I submitted it along with other important files, so it has been inherited in all my systems. Of course, from a home directory point of view, all my systems are the same: they have the same set of default folders and many of the same hidden profiles.

5. Don't worry about binaries

After weeks of rigorous testing of my system, I was convinced that it was absolutely unwise to submit binaries to Git. I've tried GPG encrypted password files, LibreOffice documents, JPEG, PNG, and so on. I even have a script that unzips the LibreOffice file before adding it to Git, extracts the XML from it, so that only the XML is committed, and then rebuilds the LibreOffice file so that it can continue to work in LibreOffice. My theory is that submitting a XML will make the Git repository smaller than using an ZIP file (an LibreOffice document is actually a ZIP file).

To my surprise, I found that the occasional submission of binaries did not significantly increase the size of my Git repository. I've been using Git for a long time, and I know that if I have to commit gigabytes of binary data, my repository will be affected, but occasionally submitting a few binaries is not an emergency to avoid at all costs.

With this confidence, I added font OTF and TTF files to my standard main repository, as well as .face files for GDM and other occasionally small binary Blob files. Don't think too much and don't waste time avoiding it. Just submit it.

6. Use private repositories

Even if the trustee provides a private account, do not submit your home directory to the public Git repository. If you have SSH keys, GPG keychains, and GPG encrypted files like me, these files should not appear on anyone's server, but on my own server.

I run a local Git server on the raspberry pie (which is easier than you think), so I can update any computer at home at any time. I'm a teleworker, so it's usually enough, but I can also access my computer through a virtual private network when I travel.

7. Remember to push

The characteristic of Git is that it will push changes to your server only when you tell it to push changes. If you are a regular user of Git, this process may be natural to you. For new users who may be used to Nextcloud or Syncthing automatic synchronization, this may take some time to get used to.

The above is all the contents of the article "what are the Git skills for managing home directories in linux". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.