diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-06-14 15:08:43 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-06-14 15:08:43 +0000 |
| commit | 9b8269e5708ba1c38610189f84cf7224b640c0ed (patch) | |
| tree | 70916a0afcfd90ed5425a80bab7f6bedca13d622 /doc/development/geo/framework.md | |
| parent | 7a124e225ea58c2a432dd29f82ba682963886383 (diff) | |
| download | gitlab-ce-9b8269e5708ba1c38610189f84cf7224b640c0ed.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/geo/framework.md')
| -rw-r--r-- | doc/development/geo/framework.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/geo/framework.md b/doc/development/geo/framework.md index 7738daee3bc..18774b9b3fd 100644 --- a/doc/development/geo/framework.md +++ b/doc/development/geo/framework.md @@ -59,7 +59,7 @@ naming conventions: consume) events. It takes care of the communication between the primary site (where events are produced) and the secondary site (where events are consumed). The engineer who wants to incorporate - Geo in their feature will use the API of replicators to make this + Geo in their feature uses the API of replicators to make this happen. - **Geo Domain-Specific Language**: @@ -99,7 +99,7 @@ end The class name should be unique. It also is tightly coupled to the table name for the registry, so for this example the registry table -will be `package_file_registry`. +is `package_file_registry`. For the different data types Geo supports there are different strategies to include. Pick one that fits your needs. |