mirror of
https://github.com/MarginaliaSearch/MarginaliaSearch.git
synced 2025-02-24 05:18:58 +00:00
4772e0b59d
Before the gRPC migration, the system would serve both public and internal requests over HTTP, but distinguish the two using path prefixes and a few HTTP Headers (X-Public, X-Context) added by the reverse proxy to prevent misconfigurations. Since internal requests meaningfully no longer use HTTP, this convention is just an obstacle now, adding the need to always run the system behind a reverse proxy that rewrites the paths. The change removes the path prefix, and updates the docker templates to reflect the change. This will require a migration for existing systems. |
||
|---|---|---|
| .. | ||
| java/nu/marginalia/control | ||
| resources | ||
| test/nu/marginalia/control/svc | ||
| build.gradle | ||
| readme.md | ||
Control Service
The control service provides an operator's user interface. By default, this interface is exposed on port 8081. It does not offer any sort of access control or authentication.
The control service will itself execute tasks that affect the entire system, but delegate node-specific tasks to the corresponding to the execution subsystem.
Conceptually the application is broken into three parts:
- Application specific tasks relate to the high level abstractions such as blacklisting and API keys
- System tasks relate to low level abstractions such as the message queue and event log.
- Node tasks relate to index node specific tasks, such as crawling and indexing.
Central Classes
See Also
- processes
- libraries/message-queue - The Message Queue and Actor abstractions