[ci skip] Update Geo docs to reflect that is synced

parent a7e227e1
...@@ -250,6 +250,8 @@ Currently, this is what is synced: ...@@ -250,6 +250,8 @@ Currently, this is what is synced:
* Git repositories * Git repositories
* Wikis * Wikis
* LFS objects * 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 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`) 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. ...@@ -12,12 +12,10 @@ manually [promote a secondary node](disaster-recovery.md) into primary.
## What data is replicated to a secondary node? ## What data is replicated to a secondary node?
We currently replicate project repositories, LFS objects and the whole We currently replicate project repositories, LFS objects, generated
database. This means user accounts, issues, merge requests, groups, project attachments / avatars and the whole database. This means user accounts,
data, etc., will be available for query. issues, merge requests, groups, project data, etc., will be available for
We currently don't replicate user generated attachments / avatars or any query. We currently don't replicate artifact data (`shared/folder`).
other file in `public/upload`. We also don't replicate artifact data
data (`shared/folder`).
## Can I git push to a secondary node? ## 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