Services¶
RabbitMQ¶
See also
Having trouble? See Troubleshoot.
This project uses a direct exchange in the same way as the default exchange, in which every queue is bound using a routing key that is the same as the queue’s name.
In each worker, the queue name and binding key is set by consume_routing_key
. The routing key of published messages is set by routing_key
. Queue names and routing keys are prefixed by the exchange name, set by the RABBIT_EXCHANGE_NAME
environment variable.
Worker/Command |
Queue (input) |
Message routing key (output) |
Sample message |
---|---|---|---|
|
N/A |
|
add command |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
N/A |
N/A |
|
|
N/A |
N/A |
PostgreSQL¶
Tables¶
Table |
Description |
|
|
---|---|---|---|
|
Extracted collections |
|
|
|
Extracted compiled releases |
|
|
|
Field-level check results |
|
|
|
Field-level check examples |
|
|
|
Compiled release-level check results |
|
|
|
Compiled release-level check examples |
|
|
|
Dataset-level check results |
|
N/A |
|
Time-based check results |
|
N/A |
|
Progress of datasets’ processing (see State machine) |
|
|
|
Progress of items’ processing (see State machine) |
|
|