Klaas van Schelven eb23d44962 Enforce a single pc_registry for a single ingesting process
Using a pid-file that's implied by the ingestion directory.

We do this in `get_pc_registry`, i.e. on the first request. This means failure is
in the first request on the 2nd process.

Why not on startup? Because we don't have a configtest or generic on-startup location
(yet). Making _that_ could be another source of fragility, and getting e.g. the nr
of processes might be non-trivial / config-dependent.
2024-07-09 13:14:27 +02:00
2024-06-13 13:23:14 +02:00
2024-03-30 11:56:29 +01:00
2024-06-17 11:08:29 +02:00
2024-06-14 12:51:31 +02:00
2024-06-14 10:29:10 +02:00
2024-05-16 10:31:59 +02:00
2024-05-27 13:54:01 +02:00
2024-01-04 20:37:26 +01:00
2023-10-29 16:43:39 +01:00
2024-06-03 22:30:10 +02:00
2024-05-15 13:32:11 +02:00
2024-05-27 13:54:02 +02:00
2024-03-20 17:37:27 +01:00
Description
No description provided
Readme 6.2 MiB
Languages
Python 80.6%
HTML 17.5%
CSS 0.9%
JavaScript 0.6%
Shell 0.3%
Other 0.1%