mirror of
https://github.com/MarginaliaSearch/MarginaliaSearch.git
synced 2025-02-24 05:18:58 +00:00
d84a2c183f
The crawl spec abstraction was used to upload lists of domains into the system for future crawling. This was fairly clunky, and it was difficult to understand what was going to be crawled. Since a while back, a new domains listing view has been added to the control view that allows direct access to the domains table. This is much preferred and means the operator can directly manage domains without specs. This commit removes the crawl spec abstraction from the code, and changes the GUI to direct to the domains list instead. |
||
|---|---|---|
| .. | ||
| 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