mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
提交译文
This commit is contained in:
stevenzdg988
parent
32b62d8300
commit
4dcfe5707d
@ -7,54 +7,50 @@
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
7 Git tips for managing your home directory
|
||||
7个管理家目录的 Git 技巧
|
||||
======
|
||||
Here is how I set up Git to manage my home directory.
|
||||
![Houses in a row][1]
|
||||
这是我怎样设置 Git 来管理我的家目录的方法。
|
||||
![一排房子][1]
|
||||
|
||||
I have several computers. I've got a laptop at work, a workstation at home, a Raspberry Pi (or four), a [Pocket CHIP][2], a [Chromebook running various forms of Linux][3], and so on. I used to set up my user environment on each computer by more or less following the same steps, and I often told myself that I enjoyed that each one was slightly unique. For instance, I use [Bash aliases][4] more often at work than at home, and the helper scripts I use at home might not be useful at work.
|
||||
我有几台电脑。我有一台笔记本电脑在工作，一台工作站在家里，一台 Raspberry Pi（或四台），一台 [Pocket CHIP][2]，一台 [运行各种不同的 Linux 的 Chromebook][3]，等等。我过去常常按照相同的步骤或多或少地在每台计算机上设置我的用户环境，而且我经常告诉自己，我喜欢每台计算机都略微独特。例如，我在工作中比在家里更经常使用 [Bash 别名][4]，并且我在家里使用的帮助脚本可能对工作没有用。
|
||||
|
||||
Over the years, my expectations across devices began to merge, and I'd forget that a feature I'd built up on my home machine wasn't ported over to my work machine, and so on. I needed a way to standardize my customized toolkit. The answer, to my surprise, was Git.
|
||||
这些年来，我对各种设备的期望开始相融，而我忘记了我在家用计算机上建立的功能没有移植到我的工作计算机上，诸如此类。我需要一种标准化我的自定义工具包的方法。使我感到意外的答案是 Git。
|
||||
|
||||
Git is version-tracker software. It's famously used by the biggest and smallest open source projects and even by the largest proprietary software companies. But it was designed for source code—not a home directory filled with music and video files, games, photos, and so on. I'd heard of people managing their home directory with Git, but I assumed that it was a fringe experiment done by coders, not real-life users like me.
|
||||
Git 是版本跟踪器软件。它著名于使用在最大和最小的开源项目，甚至最大的专利软件公司。但是它是为源代码设计的，而不是一个充满音乐和视频文件，游戏，照片等的家目录。我听说有人使用 Git 管理其家目录，但我认为这是编码人员进行的一项附带实验，而不是像我这样的现实生活中的用户。
|
||||
|
||||
Managing my home directory with Git has been an evolving process. I've learned and adapted along the way. Here are the things you might want to keep in mind should you decide to manage your home directory with Git.
|
||||
用 Git 管理我的家目录是一个不断发展的过程。随着时间的推移我一直在学习和适应。如果您决定使用 Git 管理家目录，则可能需要记住以下几点。
|
||||
|
||||
### 1\. Text and binary locations
|
||||
### 1\. 文本和二进制位置
|
||||
|
||||
![home directory][5]
|
||||
![家目录][5]
|
||||
|
||||
(Seth Kenlon, [CC BY-SA 4.0][6])
|
||||
|
||||
When managed by Git, your home directory becomes something of a no-man 's-land for everything but configuration files. That means when you open your home directory, you should see nothing but a list of predictable directories. There shouldn't be any stray photos or LibreOffice documents, and no "I'll put this here for just a minute" files.
|
||||
当由 Git 管理时，除了配置文件之外，您的家目录对于所有内容而言都是"无人之地"。这意味着当您打开主目录时，除了可预见的目录的列表之外，您什么都看不到。不应有任何无主的照片或 LibreOffice 文档，也不应有 “我将其放在此处仅一分钟(临时)” 的文件。
|
||||
|
||||
The reason for this is simple: when you manage your home directory with Git, everything in your home directory that's _not_ being committed becomes noise. Every time you do a `git status`, you'll have to scroll past any file that Git isn't tracking, so it's vital that you keep those files in subdirectories (which you add to your `.gitignore` file).
|
||||
原因很简单：使用 Git 管理家目录时，家目录中所有 _未_ 提交的内容都会变得杂乱无章。每次执行 `git status` 时，您都必须滚动到过去任何 Git 未跟踪的文件，因此将这些文件保存在子目录（添加到 `.gitignore` 文件中）至关重要。
|
||||
|
||||
Many Linux distributions provide a set of default directories:
|
||||
许多 Linux 发行版提供了一组默认目录：
|
||||
|
||||
* Documents
|
||||
* Downloads
|
||||
* Music
|
||||
* Photos
|
||||
* Templates
|
||||
* Videos
|
||||
* 文档
|
||||
* 下载
|
||||
* 音乐
|
||||
* 相片
|
||||
* 模板
|
||||
* 视频
|
||||
|
||||
如果需要，您可以创建更多。例如，我区分创作的音乐（音乐）和购买的聆听音乐（专辑）。同样，我的 Cinema (电影)目录包含其他人的电影，而 Videos (视频目录)包含我需要编辑的视频文件。换句话说，我的默认目录结构比大多数 Linux 发行版提供的默认集更详细，但是我认为这样做有好处。如果没有适合您的目录结构，由于缺少更好的存放位置，您将更有可能将其存放在家目录中，因此请提前考虑并计划适合您的工作目录。您以后总是可以添加更多，但是最好先开始擅长的。
|
||||
|
||||
### 2\. 设置最优的 `.gitignore`
|
||||
|
||||
You can create more if you need them. For instance, I differentiate between the music I create (Music) and the music I purchase to listen to (Albums). Likewise, my Cinema directory contains movies by other people, while Videos contains video files I need for editing. In other words, my default directory structure has more granularity than the default set provided by most Linux distributions, but I think there's a benefit to that. Without a directory structure that works for you, you'll be more likely to just stash stuff in your home directory, for lack of a better place for it, so think ahead and plan out directories that work for you. You can always add more later, but it's best to start strong.
|
||||
|
||||
### 2\. Setting up your very best .gitignore
|
||||
|
||||
Once you've cleaned up your home directory, you can instantiate it as a Git repository as usual:
|
||||
|
||||
清理家目录后，您可以像往常一样将其作为 Git 存储库实例化：
|
||||
|
||||
```
|
||||
$ cd
|
||||
$ git init .
|
||||
```
|
||||
|
||||
Your Git repository contains nothing yet, so everything in your home directory is untracked. Your first job is to sift through the list of untracked files and determine what you want to remain untracked. To see untracked files:
|
||||
|
||||
您的 Git 信息库还没有任何内容，因此您的家目录中的所有内容均未被跟踪。您的第一项工作是筛选未跟踪文件的列表，并确定要保持未跟踪状态的文件。要查看未跟踪的文件：
|
||||
|
||||
```
|
||||
$ git status
|
||||
@ -69,52 +65,51 @@ $ git status
|
||||
[...]
|
||||
```
|
||||
|
||||
Depending on how long you've been using your home directory, this list may be long. The easy ones are the directories you decided on in the first step. By adding these to a hidden file called `.gitignore`, you tell Git to stop listing them as untracked files and never to track them:
|
||||
|
||||
根据您使用家目录的时间长短，此列表可能很长。简单的目录是您在第一步中确定的目录。通过将它们添加到名为 `.gitignore` 的隐藏文件中，您告诉 Git 停止将它们列为未跟踪文件，并且从不对其进行跟踪：
|
||||
|
||||
```
|
||||
`$ \ls -lg | grep ^d | awk '{print $8}' >> ~/.gitignore`
|
||||
```
|
||||
|
||||
With that done, go through the remaining untracked files shown by `git status` and determine whether any other files warrant exclusion. This process helped me discover several stale old configuration files and directories, which I ended up trashing altogether, but also some that were very specific to one computer. I was fairly strict here because many configuration files do better when they're auto-generated. For instance, I never commit my KDE configuration files because many contain information like recent documents and other elements that don't exist on another machine.
|
||||
完成后，浏览 `git status` 所示的其余未跟踪文件，并确定是否有其他文件需要授权排除。这个过程帮助我发现了几个陈旧的配置文件和目录，这些文件和目录最终被我全部丢弃了，而且还发现了一些特定于一台计算机的文件和目录。我在这里非常严格，因为许多配置文件在自动生成时会做得更好。例如，我从未提交过 KDE 配置文件，因为许多文件包含诸如最新文档之类的信息以及其他机器上不存在的其他元素。
|
||||
|
||||
I track my personalized configuration files, scripts and utilities, profile and Bash configs, and cheat sheets and other snippets of text that I refer to frequently. If the software is mostly responsible for maintaining a file, I ignore it. And when in doubt about a file, I ignore it. You can always un-ignore it later (by removing it from your `.gitignore` file).
|
||||
我跟踪我的个性化配置文件，脚本和实用程序，配置文件和 Bash 配置以及速查表和我经常引用的其他文本片段。如果该软件主要负责维护文件，则将其忽略。当对文件有疑问时，我将其忽略。您以后总是可以取消忽略它（通过从 .gitignore 文件中删除它）。
|
||||
|
||||
### 3\. Get to know your data
|
||||
### 3\. 了解您的数据
|
||||
|
||||
I'm on KDE, so I use the open source scanner [Filelight][7] to get an overview of my data. Filelight gives you a chart that lets you see the size of each directory. You can navigate through each directory to see what's taking up all the space and then backtrack to investigate elsewhere. It's a fascinating view of your system, and it lets you see your files in a completely new light.
|
||||
我正在使用 KDE，因此我使用开源扫描程序 [Filelight][7] 来获取我的数据概述。Filelight 为您提供了一个图表，可让您查看每个目录的大小。您可以浏览每个目录以查看占用了所有空间的内容，然后回溯调查其他地方。这是您系统的迷人视图，它使您可以以全新的方式查看文件。
|
||||
|
||||
![Filelight][8]
|
||||
|
||||
(Seth Kenlon, [CC BY-SA 4.0][6])
|
||||
|
||||
Use Filelight or a similar utility to find unexpected caches of data you don't need to commit. For instance, the KDE file indexer (Baloo) generates quite a lot of data specific to its host that I definitely wouldn't want to transport to another computer.
|
||||
使用 Filelight 或类似的实用程序查找不需要提交的意外数据缓存。例如，KDE 文件索引器（Baloo）生成了大量特定于其主机的数据，我绝对不希望将其传输到另一台计算机。
|
||||
|
||||
### 4\. Don't ignore your .gitignore file
|
||||
### 4\. 不要忽略您的 .gitignore 文件
|
||||
|
||||
On some projects, I tell Git to ignore my `.gitignore` file because what I want to ignore is sometimes specific to my working directory, and I don't presume other developers on the same project need me to tell them what their `.gitignore` file ought to look like. Because my home directory is for my use only, I do _not_ ignore my home's `.gitignore` file. I commit it along with other important files, so it's inherited across all of my systems. And of course, all of my systems are identical from the home directory's viewpoint: they have the same set of default folders and many of the same hidden configuration files.
|
||||
在某些项目中，我告诉 Git 忽略我的`.gitignore`文件，因为有时我要忽略的内容特定于我的工作目录，并且我不认为同一项目中的其他开发人员需要我告诉他们的 `.gitignore` 文件的内容应该看起来像什么。因为我的家目录仅供我使用，所以我 _不_ 会忽略我的家目录的 `.gitignore` 文件。我将其与其他重要文件一起提交，因此它已在我的所有系统中被继承。当然，从家目录的角度来看，我所有的系统都是相同的：它们具有相同的默认文件夹集和许多相同的隐藏配置文件。
|
||||
|
||||
### 5\. Don't fear the binary
|
||||
### 5\. 不要担心二进制文件
|
||||
|
||||
I put my system through weeks and weeks of rigorous testing, convinced that it was _never_ wise to commit binary files to Git. I tried GPG encrypted password files, I tried LibreOffice documents, JPEGs, PNGs, and more. I even had a script that unarchived LibreOffice files before adding them to Git, extracted the XML inside so I could commit just the XML, and then rebuilt the LibreOffice file so that I could work on it within LibreOffice. My theory was that committing XML would render a smaller Git repository than a ZIP file (which is all a LibreOffice document really is).
|
||||
我对系统进行了数周的严格测试，确信将二进制文件提交到 Git 是绝对不明智的。我尝试了 GPG 加密的密码文件，尝试了 LibreOffice 文档，JPEG，PNG 等等。我甚至有一个脚本，可以在将 LibreOffice 文件添加到 Git 之前取消存档，然后提取其中的 XML，以便仅提交 XML，然后重新构建 LibreOffice 文件，以便可以在 LibreOffice 中继续工作。我的理论是，提交 XML 会比使用 ZIP 文件（这实际上是 LibreOffice 文档的全部）提供一个更小的 Git 存储库。
|
||||
|
||||
To my great surprise, I found that committing a few binary files every now and then did not substantially increase the size of my Git repository. I've worked with Git long enough to know that if I were to commit gigabytes of binary data, my repository would suffer, but the occasional binary file isn't an emergency to avoid at all costs.
|
||||
令我惊讶的是，我发现不时提交一些二进制文件并没有实质性地增加我的 Git 存储库的大小。我使用 Git 已经很长时间了，以至于如果我要提交千兆字节的二进制数据，我的存储库将会遭受损失，但是偶尔的二进制文件并不是不惜一切代价避免的紧急情况。
|
||||
|
||||
Armed with this new confidence, I add font OTF and TTF files to my standard home repo, my `.face` file for GDM, and other incidental minor binary blobs. Don't overthink it, don't waste time trying to avoid it; just commit it.
|
||||
有了这种信心，我将字体 OTF 和 TTF 文件添加到我的标准主存储库，GDM 的`.face`文件以及其他附带的次要二进制 Blob 文件。不要想太多，不要浪费时间去避免它。只需提交即可。
|
||||
|
||||
### 6\. Use a private repo
|
||||
### 6\. 使用私有存储库
|
||||
|
||||
Don't commit your home directory to a public Git repository, even if the host offers private accounts. If you're like me, you have SSH keys and GPG keychains and GPG-encrypted files that ought not end up on anybody's server but my own.
|
||||
即使主机提供私人帐户，也不要将您的主目录提交到公共 Git 存储库。如果您像我一样，拥有 SSH 密钥，GPG 密钥链和 GPG 加密的文件，这些属于自己的文件不应该出现在任何人的服务器上。
|
||||
|
||||
I [run a local Git server][9] on a Raspberry Pi (it's easier than you think), so I can update any computer any time I'm home. I'm a remote worker, so that's usually good enough, but I can also reach the computer when traveling over my [VPN][10].
|
||||
我在 Raspberry Pi 上[运行本地 Git 服务器][9]（这比您想象的要容易），因此我可以在家里时随时更新任何一台计算机。我是一名远程工作者，所以通常情况下就足够了，但是我也可以通过 [VPN][10] 访问计算机。
|
||||
|
||||
### 7\. Remember to push
|
||||
### 7\. 要记得推送
|
||||
|
||||
The thing about Git is that it only pushes changes to your server when you tell it to. If you're a longtime Git user, this process is probably natural to you. For new users who might be accustomed to the automatic synchronization in Nextcloud or Syncthing, this may take some getting used to.
|
||||
关于 Git ，仅当您通知服务器时，它才会将更改推送到您的服务器。如果您是 Git 的长期用户，则此过程可能对您很自然。对于可能习惯于 Nextcloud 或 Syncthing 自动同步的新用户，这可能需要一些时间来适应。
|
||||
|
||||
### Git at home
|
||||
### Git 家目录
|
||||
|
||||
Managing my common files with Git hasn't just made life more convenient across devices. Knowing that I have a full history for all my configurations and utility scripts encourages me to try out new ideas because it's always easy to roll back my changes if they turn out to be _bad_ ideas. Git has rescued me from an ill-advised umask setting in `.bashrc`, a poorly executed late-night addition to my package management script, and an it-seemed-like-a-cool-idea-at-the-time change of my [rxvt][11] color scheme—and probably a few other mistakes in my past. Try Git in your home because a home that commits together merges together.
|
||||
使用 Git 管理我的通用文件并没有使跨设备的生活更加便利。知道我对所有配置和实用程序脚本都有完整的历史记录，这会鼓励我尝试新的想法，因为如果结果变得 _很糟糕_，则很容易回滚我的更改。 Git 已将我从在 `.bashrc` 文件欠考虑的掩码设置中解救出来，对于我的软件包管理脚本糟糕的深夜附加物，并且更改 [rxvt][11] 配色方案以及过去的其他一些错误这时看起来像一个很酷的想法。在家(目录)中尝试 Git，因为一起提交的家(目录)会合并在一起。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user