mirror of
https://github.com/MarginaliaSearch/MarginaliaSearch.git
synced 2025-02-24 13:19:02 +00:00
1d34224416
Look, this will make the git history look funny, but trimming unnecessary depth from the source tree is a very necessary sanity-preserving measure when dealing with a super-modularized codebase like this one. While it makes the project configuration a bit less conventional, it will save you several clicks every time you jump between modules. Which you'll do a lot, because it's *modul*ar. The src/main/java convention makes a lot of sense for a non-modular project though. This ain't that. |
||
|---|---|---|
| .. | ||
| 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 executor-service via the executor-api.
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