Merge branch 'doc/gitlab-geo-86' into 'master'

GitLab Geo: documentation changes for 8.6

Improved documentations for GitLab Geo (#76) in 8.6 release.

* Removed some limitations
* Added recommendation to try Geo with 8.6
* Changed link in admin screen to a valid one :)

See merge request !287

CHANGELOG-EE

@@ -14,6 +14,10 @@ v 8.6.0 (unreleased)
   - [Elastic] More accurate as_indexed_json (More stable database indexer)
   - [Elastic] Fix: Don't index newly created system messages and awards
   - [Elastic] Fixed exception on branch removing
+  - GitLab Geo: OAuth authentication
+  - GitLab Geo: Wiki synchronization
+  - GitLab Geo: ReadOnly Middleware improvements
+  - GitLab Geo: SSH Keys synchronization
 
 v 8.5.8
   - GitLab Geo: Documentation

app/views/admin/geo_nodes/index.html.haml

@@ -3,7 +3,7 @@
   Geo Nodes
 
 %p.light
-  With #{link_to 'GitLab Geo', help_page_path('gitlab-geo', 'overview'), class: 'vlink'} you can install a special
+  With #{link_to 'GitLab Geo', help_page_path('gitlab-geo', 'README'), class: 'vlink'} you can install a special
   read-only and replicated instance anywhere.
 
 %hr

doc/README.md

@@ -86,7 +86,7 @@ be linked with your base image. Below is a list of examples you may use:
 - [GitLab Pages configuration](pages/administration.md)
 - [Elasticsearch](integration/elasticsearch.md) Enable Elasticsearch
 - [GitLab Performance Monitoring](monitoring/performance/introduction.md) Configure GitLab and InfluxDB for measuring performance metrics
-- [GitLab GEO](administration/gitlab-geo/README.md) Configure GitLab GEO, a
+- [GitLab GEO](gitlab-geo/README.md) Configure GitLab GEO, a
   secondary read-only GitLab instance
 
 ## Contributor documentation

doc/administration/gitlab-geo/README.md → doc/gitlab-geo/README.md

 # GitLab Geo
 
 > **Note:**
-This feature was introduced in GitLab 8.5 EE.
+This feature was introduced in GitLab 8.5 EE as Alpha.
+We recommend you use with at least GitLab 8.6 EE.
 
 GitLab Geo allows you to replicate your GitLab instance to other geographical
 locations as a read-only fully operational version.
@@ -65,13 +66,9 @@ there are a few things to consider:
 
 ## Current limitations
 
-- The secondary node cannot be used for browsing
 - You cannot push code to secondary nodes
 - Git LFS is not supported yet
 - Git Annex is not supported yet
-- Wiki's are not being replicated yet
-- Git clone from secondaries by HTTP/HTTPS only (ssh-keys aren't being
-  replicated yet)
 
 ## Frequently Asked Questions