Commit 59ac3360 authored by Robert Speicher's avatar Robert Speicher

Merge branch 'geo/update-docs' into 'master'

Update Geo docs to reflect what is synced

[ci skip]

See merge request !1603
parents 9b99b3e4 df0526fb
......@@ -250,6 +250,8 @@ Currently, this is what is synced:
* Git repositories
* Wikis
* LFS objects
* Issue, merge request, and comment attachments
* User, group, and project avatars
You can monitor the status of the syncing process on a secondary node
by visiting the primary node's **Admin Area ➔ Geo Nodes** (`/admin/geo_nodes`)
......
......@@ -12,12 +12,10 @@ manually [promote a secondary node](disaster-recovery.md) into primary.
## What data is replicated to a secondary node?
We currently replicate project repositories, LFS objects and the whole
database. This means user accounts, issues, merge requests, groups, project
data, etc., will be available for query.
We currently don't replicate user generated attachments / avatars or any
other file in `public/upload`. We also don't replicate artifact data
data (`shared/folder`).
We currently replicate project repositories, LFS objects, generated
attachments / avatars and the whole database. This means user accounts,
issues, merge requests, groups, project data, etc., will be available for
query. We currently don't replicate artifact data (`shared/folder`).
## Can I git push to a secondary node?
......
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