Commit Graph

6 Commits

Author SHA1 Message Date
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
Klaas van Schelven 371c86b552 Docs for single-server: cleanup by doing a full replay 2024-05-17 12:23:17 +02:00
Klaas van Schelven cb62ec7c58 Docs; WIP for single-server-deployment 2024-05-16 13:11:19 +02:00
Klaas van Schelven 0f0a4f996c DDD: whitenoise
Why?

> One is that WhiteNoise is designed to work in situations where Apache, nginx
> and the like aren’t easily available. But more importantly, it’s easy to
> underestimate what’s involved in serving static files correctly

We deal with both these situations:

* for local development, we recommend running with DEBUG=False and still want to
  sever staticfiles

* for deploying using nginx/whatever, I'd like to keep my instructions as simple
  as possible, and doing this right once (in whitenoise) saves us from having to
  come up with the right instructions for a bunch of webservers.
2024-05-16 10:31:59 +02:00
Klaas van Schelven 5bc3a54e71 Documentation Driven Development: getting started guide
excluding static files
2024-05-16 10:09:55 +02:00
Klaas van Schelven 7a6dc42478 First version of local-install tutorial 2024-05-16 09:08:15 +02:00