Commit 7e158317 authored by Evan Read's avatar Evan Read

Merge branch 'docs-fix-links-3' into 'master'

Docs: Cleaning up various links

See merge request gitlab-org/gitlab-ce!23110
parents 0b48c0ea 4cee901d
...@@ -23,8 +23,7 @@ ...@@ -23,8 +23,7 @@
1. Code should be written in [US English][us-english] 1. Code should be written in [US English][us-english]
This is also the style used by linting tools such as This is also the style used by linting tools such as
[RuboCop](https://github.com/bbatsov/rubocop), [RuboCop](https://github.com/bbatsov/rubocop) and [Hound CI](https://houndci.com).
[PullReview](https://www.pullreview.com/) and [Hound CI](https://houndci.com).
--- ---
......
...@@ -97,7 +97,7 @@ Follow the below instructions to ensure you use the most up to date requirements ...@@ -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 #### 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 # Login to MySQL
mysql -u root -p mysql -u root -p
...@@ -134,7 +134,7 @@ We need to check, enable and maybe convert your existing GitLab DB tables to the ...@@ -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. > 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:** 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. 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 ...@@ -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** - **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: 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 ...@@ -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). (sometimes less if the value contains multibyte characters).
Details can be found in the [PostgreSQL][postgres-text-type] and 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 [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 [ce-38152]: https://gitlab.com/gitlab-org/gitlab-ce/issues/38152
...@@ -30,7 +30,7 @@ clients at your disposal. ...@@ -30,7 +30,7 @@ clients at your disposal.
### Installing the SSH client for Windows 8.1 and Windows 7 ### 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 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 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. `ssh-keygen` command that is useful to create SSH keys as you'll learn below.
......
...@@ -396,4 +396,4 @@ settings are recommended: ...@@ -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 - `unknown_git` user will be used as the commit author if the GitLab user does not exist in
Perforce Helix. 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).
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment