diff options
Diffstat (limited to 'doc/administration')
7 files changed, 12 insertions, 12 deletions
diff --git a/doc/administration/geo/replication/configuration.md b/doc/administration/geo/replication/configuration.md index c3d45d51ea6..5c8ad18a4df 100644 --- a/doc/administration/geo/replication/configuration.md +++ b/doc/administration/geo/replication/configuration.md @@ -171,7 +171,7 @@ keys must be manually replicated to the **secondary** node. sudo -i ``` -1. Edit `/etc/gitlab/gitlab.rb` and add a **unique** name for your node. You will need this in the next steps: +1. Edit `/etc/gitlab/gitlab.rb` and add a **unique** name for your node. You will need this in the next steps: ```ruby # The unique identifier for the Geo node. diff --git a/doc/administration/geo/replication/faq.md b/doc/administration/geo/replication/faq.md index 8a3439d2aaa..2405e2cbfd2 100644 --- a/doc/administration/geo/replication/faq.md +++ b/doc/administration/geo/replication/faq.md @@ -45,7 +45,7 @@ query. ## Can I `git push` to a **secondary** node? -Yes! Pushing directly to a **secondary** node (for both HTTP and SSH, including Git LFS) was [introduced](https://about.gitlab.com/releases/2018/09/22/gitlab-11-3-released/) in [GitLab Premium](https://about.gitlab.com/pricing/#self-managed) 11.3. +Yes! Pushing directly to a **secondary** node (for both HTTP and SSH, including Git LFS) was [introduced](https://about.gitlab.com/releases/2018/09/22/gitlab-11-3-released/) in [GitLab Premium](https://about.gitlab.com/pricing/#self-managed) 11.3. ## How long does it take to have a commit replicated to a **secondary** node? diff --git a/doc/administration/gitaly/praefect.md b/doc/administration/gitaly/praefect.md index 2f80dd66548..073e2010fd2 100644 --- a/doc/administration/gitaly/praefect.md +++ b/doc/administration/gitaly/praefect.md @@ -227,7 +227,7 @@ remember to run `sudo gitlab-ctl reconfigure` again before trying the #### Gitaly -Next we will configure each Gitaly server assigned to Praefect. Configuration for these +Next we will configure each Gitaly server assigned to Praefect. Configuration for these is the same as a normal standalone Gitaly server, except that we use storage names and auth tokens from Praefect instead of GitLab. diff --git a/doc/administration/operations/moving_repositories.md b/doc/administration/operations/moving_repositories.md index a11bce9aa02..2b9ef02ec42 100644 --- a/doc/administration/operations/moving_repositories.md +++ b/doc/administration/operations/moving_repositories.md @@ -16,9 +16,9 @@ source and the target.** ## Target directory is empty: use a tar pipe If the target directory `/mnt/gitlab/repositories` is empty the -simplest thing to do is to use a tar pipe. This method has low +simplest thing to do is to use a tar pipe. This method has low overhead and tar is almost always already installed on your system. -However, it is not possible to resume an interrupted tar pipe: if +However, it is not possible to resume an interrupted tar pipe: if that happens then all data must be copied again. ```shell @@ -82,7 +82,7 @@ repository at a time. In addition to rsync we will use [GNU Parallel](http://www.gnu.org/software/parallel/). This utility is not included in GitLab so you need to install it yourself with apt -or yum. Also note that the GitLab scripts we used below were added +or yum. Also note that the GitLab scripts we used below were added in GitLab 8.1. ** This process does not clean up repositories at the target location that no diff --git a/doc/administration/operations/unicorn.md b/doc/administration/operations/unicorn.md index a19617daaef..653fad7e24f 100644 --- a/doc/administration/operations/unicorn.md +++ b/doc/administration/operations/unicorn.md @@ -75,7 +75,7 @@ Otherwise, you can set the `GITLAB_UNICORN_MEMORY_MIN` and `GITLAB_UNICORN_MEMOR This is what a Unicorn worker memory restart looks like in unicorn_stderr.log. You see that worker 4 (PID 125918) is inspecting itself and decides to exit. The threshold memory value was 254802235 bytes, about 250MB. With GitLab this -threshold is a random value between 200 and 250 MB. The master process (PID +threshold is a random value between 200 and 250 MB. The master process (PID 117565) then reaps the worker process and spawns a new 'worker 4' with PID 127549. diff --git a/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md b/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md index d4719bb41dc..a4180eb638a 100644 --- a/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md +++ b/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md @@ -166,7 +166,7 @@ GIT_CURL_VERBOSE=1 GIT_TRACE=1 git clone <repository> # A single project project = Project.find_by_full_path('PROJECT_PATH') -# All projects in a particular namespace. Can be a username, a group +# All projects in a particular namespace. Can be a username, a group # ('gitlab-org'), or even include subgroups ('gitlab-org/distribution') namespace = Namespace.find_by_full_path('NAMESPACE_PATH') projects = namespace.all_projects @@ -997,7 +997,7 @@ gitlab_rails['env'] = { } ``` -Then `gitlab-ctl reconfigure; gitlab-ctl restart sidekiq`. The Sidekiq logs will now include additional data for troubleshooting. +Then `gitlab-ctl reconfigure; gitlab-ctl restart sidekiq`. The Sidekiq logs will now include additional data for troubleshooting. ### Sidekiq kill signals diff --git a/doc/administration/troubleshooting/linux_cheat_sheet.md b/doc/administration/troubleshooting/linux_cheat_sheet.md index 0ad1f028f20..d53745c58b3 100644 --- a/doc/administration/troubleshooting/linux_cheat_sheet.md +++ b/doc/administration/troubleshooting/linux_cheat_sheet.md @@ -133,7 +133,7 @@ sudo !! ### Memory, Disk, & CPU usage ```shell -# disk space info. The '-h' gives the data in human-readable values +# disk space info. The '-h' gives the data in human-readable values df -h # size of each file/dir and its contents in the current dir @@ -186,7 +186,7 @@ Be aware that strace can have major impacts to system performance when it is run ### The Strace Parser tool Our [strace-parser tool](https://gitlab.com/wchandler/strace-parser) can be used to -provide a high level summary of the `strace` output. It is similar to `strace -C`, +provide a high level summary of the `strace` output. It is similar to `strace -C`, but provides much more detailed statistics. MacOS and Linux binaries [are available](https://gitlab.com/gitlab-com/support/toolbox/strace-parser/-/tags), @@ -198,7 +198,7 @@ First run the tool with no arguments other than the strace output file name to g a summary of the top processes sorted by time spent actively performing tasks. You can also sort based on total time, # of syscalls made, PID #, and # of child processes using the `-S` or `--sort` flag. The number of results defaults to 25 processes, but -can be changed using the `-c`/`--count` option. See `--help` for full details. +can be changed using the `-c`/`--count` option. See `--help` for full details. ```shell $ ./strace-parser strace.txt |