MarginaliaSearch/code/services-core/control-service
Viktor Lofgren 47dfbacb00 (conf) Introduce a new concept of node profiles
Node profiles decide which actors are started, and which views are available in the control GUI.  This helps keep the system organized, and hides real-time clutter from the batch-oriented nodes.
2024-11-20 18:15:22 +01:00
..
java/nu/marginalia/control (conf) Introduce a new concept of node profiles 2024-11-20 18:15:22 +01:00
resources (conf) Introduce a new concept of node profiles 2024-11-20 18:15:22 +01:00
test/nu/marginalia/control (setup) Move some file-downloads from setup script to the first boot of the control node of the system 2024-11-06 15:28:20 +01:00
build.gradle Merge branch 'master' into term-positions 2024-09-08 10:14:43 +02:00
readme.md Clean up documentation and rename domain-links to link-graph 2024-02-28 11:40:39 +01:00

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