-
-
Notifications
You must be signed in to change notification settings - Fork 5
Architecture and design
Peter Chapman edited this page Nov 5, 2024
·
7 revisions
The Serval Sync process involves the interactions between the texts collection (Local Data), sf_project_secrets collection (Sync Data), and Serval (Remote Data). The valid states for data being present in this system could be defined as:
| Text Docs (Local Data) | Project Secrets (Sync Data) | Serval Data Files (Remote Data) | Sync State |
|---|---|---|---|
| Yes | Yes | Yes | Fully In Sync |
| No | No | No | Does Not Exist |
| Yes | No | No | Not Yet Synced |
| No | Yes | Yes | Text Deleted |
The following is a simplified flowchart describing the sync process for text docs to Serval:


The following ports are used by Scripture Forge, particularly on Development Environments:
5000 HTTP Port
5001 HTTPS Port
5002 Realtime Server port for .NET Backend (used by Jering)
5003 WS Port for ShareDB (used for ShareDB connections from port 5000)
5005 WSS Port for ShareDB (used for ShareDB connections from port 5001)