A service to replicate and serve requests for site configurations based on site ID, public IP, and the on-site lead contact's OTP.
Révision | eee9574625189b3848c887e9d88845034a412c25 (tree) |
---|---|
l'heure | 2021-10-14 00:00:53 |
Auteur | S. Seago <sseago-dev@proj...> |
Commiter | S. Seago |
Provide more detail about the makup of Manifest
@@ -7,6 +7,14 @@ | ||
7 | 7 | === What is This? |
8 | 8 | This is a Project Celadon site manifest server. This repository includes all forms of instruction needed to create a manifest server. This project is very much a work in progress. In fact, this code base is not expected to be usable until the end of development cycle 2022.2 (March 14 to May 25). Until then (at least), contribute code, sit tight, or look elsewhere. |
9 | 9 | |
10 | +==== Yeah, but What is a Project Celadon Manifest Server, Really? | |
11 | +It is: | |
12 | + | |
13 | +* apache - The interface used to communicate between the diviner server and the mongodb database | |
14 | +* mongodb - The storage backend for site manifests | |
15 | +* mongo-express - An interface for debugging and correcting minor issues with a manifest or mongodb, also hosted via Apache, but accessible only internally. | |
16 | + | |
17 | + | |
10 | 18 | === Why Make This? |
11 | 19 | Each site that comes on line has a reference configuration. Any number of things can happen to the person in charge of a project, including illness, incarceration, and death. Rather than leave such sensitive information available on a USB drive, we hold the data in a decentralized, distributed database with read-only access from the Internet. Only the primary node has write access. The selection of the primary node is beyond the scope of this document. |
12 | 20 |