From 4cee901dab76300e98fcedcb0a32f50f0d8dc105 Mon Sep 17 00:00:00 2001 From: Marcel Amirault Date: Wed, 21 Nov 2018 23:15:01 +0000 Subject: Docs: Cleaning up various links --- doc/development/contributing/style_guides.md | 3 +-- doc/install/database_mysql.md | 9 ++++----- doc/ssh/README.md | 2 +- doc/workflow/repository_mirroring.md | 2 +- 4 files changed, 7 insertions(+), 9 deletions(-) diff --git a/doc/development/contributing/style_guides.md b/doc/development/contributing/style_guides.md index fb0454db7d2..6f1ba5d62a5 100644 --- a/doc/development/contributing/style_guides.md +++ b/doc/development/contributing/style_guides.md @@ -23,8 +23,7 @@ 1. Code should be written in [US English][us-english] This is also the style used by linting tools such as -[RuboCop](https://github.com/bbatsov/rubocop), -[PullReview](https://www.pullreview.com/) and [Hound CI](https://houndci.com). +[RuboCop](https://github.com/bbatsov/rubocop) and [Hound CI](https://houndci.com). --- diff --git a/doc/install/database_mysql.md b/doc/install/database_mysql.md index 4cb8ca4f3e7..e89846107b6 100644 --- a/doc/install/database_mysql.md +++ b/doc/install/database_mysql.md @@ -97,7 +97,7 @@ Follow the below instructions to ensure you use the most up to date requirements #### Check for InnoDB File-Per-Table Tablespaces -We need to check, enable and maybe convert your existing GitLab DB tables to the [InnoDB File-Per-Table Tablespaces](http://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html) as a prerequisite for supporting **utfb8mb4 with long indexes** required by recent GitLab databases. +We need to check, enable and maybe convert your existing GitLab DB tables to the [InnoDB File-Per-Table Tablespaces](https://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html) as a prerequisite for supporting **utfb8mb4 with long indexes** required by recent GitLab databases. # Login to MySQL mysql -u root -p @@ -134,7 +134,7 @@ We need to check, enable and maybe convert your existing GitLab DB tables to the > You need **MySQL 5.5.3 or later** to perform this update. -Whatever the results of your checks above, we now need to check if your GitLab database has been created using [InnoDB File-Per-Table Tablespaces](http://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html) (i.e. `innodb_file_per_table` was set to **1** at initial setup time). +Whatever the results of your checks above, we now need to check if your GitLab database has been created using [InnoDB File-Per-Table Tablespaces](https://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html) (i.e. `innodb_file_per_table` was set to **1** at initial setup time). NOTE: **Note:** This setting is [enabled by default](http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table) since MySQL 5.6.6. @@ -163,7 +163,7 @@ Now, if you have a **different result** returned by the 2 commands above, it mea - **Case 2: a result equals to "0" OR not the same result for both commands** -Unfortunately, none or only some of your GitLab database tables use the GitLab requirement of [InnoDB File-Per-Table Tablespaces](http://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html). +Unfortunately, none or only some of your GitLab database tables use the GitLab requirement of [InnoDB File-Per-Table Tablespaces](https://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html). Let's enable what we need on the running server: @@ -297,8 +297,7 @@ GitLab database to `longtext` columns, which can persist values of up to 4GB (sometimes less if the value contains multibyte characters). Details can be found in the [PostgreSQL][postgres-text-type] and -[MySQL][mysql-text-types] manuals. +[MySQL](https://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html) manuals. [postgres-text-type]: http://www.postgresql.org/docs/9.2/static/datatype-character.html -[mysql-text-types]: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html [ce-38152]: https://gitlab.com/gitlab-org/gitlab-ce/issues/38152 diff --git a/doc/ssh/README.md b/doc/ssh/README.md index c5b7813b285..9114b8d8417 100644 --- a/doc/ssh/README.md +++ b/doc/ssh/README.md @@ -30,7 +30,7 @@ clients at your disposal. ### Installing the SSH client for Windows 8.1 and Windows 7 The easiest way to install Git and the SSH client on Windows 8.1 and Windows 7 -is [Git for Windows](https://gitforwindows.com). It provides a BASH +is [Git for Windows](https://gitforwindows.org). It provides a BASH emulation (Git Bash) used for running Git from the command line and the `ssh-keygen` command that is useful to create SSH keys as you'll learn below. diff --git a/doc/workflow/repository_mirroring.md b/doc/workflow/repository_mirroring.md index 7eb324e3ece..e259e6fe50c 100644 --- a/doc/workflow/repository_mirroring.md +++ b/doc/workflow/repository_mirroring.md @@ -396,4 +396,4 @@ settings are recommended: - `unknown_git` user will be used as the commit author if the GitLab user does not exist in Perforce Helix. -Read about [Git Fusion settings on Perforce.com](https://www.perforce.com/perforce/doc.current/manuals/git-fusion/Content/Git-Fusion/section_zdp_zz1_3l.html). +Read about [Git Fusion settings on Perforce.com](https://www.perforce.com/perforce/doc.current/manuals/git-fusion/Content/Git-Fusion/section_vss_bdw_w3.html#section_zdp_zz1_3l). -- cgit v1.2.1