60 Commits

Author SHA1 Message Date
Klaas van Schelven
918b1ef54c Add ids to 2 system-checks 2025-02-18 12:10:32 +01:00
Klaas van Schelven
3cb07246b9 Add system-check for EVENT_STORAGES setting 2025-02-18 12:08:05 +01:00
Klaas van Schelven
97e54868c9 showstat: warning about eviction 2025-02-17 13:41:21 +01:00
Klaas van Schelven
5263980f54 showstat: digestion_speed 2025-02-17 13:21:41 +01:00
Klaas van Schelven
01325ae0f3 Add migrate command that always shows timings 2025-02-14 10:15:23 +01:00
Klaas van Schelven
561c1d324a event.data getters
in preparation for scenarios where the dumped data is not stored in the DB
2025-02-07 17:09:36 +01:00
Klaas van Schelven
51fced662a Add event_count showstat 2025-02-07 11:13:15 +01:00
Klaas van Schelven
fd7eae681d Remove migrations directory from modelless apps 2025-02-03 13:05:20 +01:00
Klaas van Schelven
cf23ba707e Warn about top-level settings 2025-01-24 11:40:13 +01:00
Klaas van Schelven
ae9cb209a5 Create 'bsmain' (for bugsink-main) app to hold commands
As had been noted on some of the commands, 'ingest' was not the best place for
them.  However, [project-level apps are not supported in
Django](https://forum.djangoproject.com/t/allow-project-to-have-management-commands/5220/2)
So just create a 'main' app. I want to qualify it as 'myproject-main' though, to avoid
further unqualified global namespace pollution. And I want to avoid prefixing with 'bugsink'
b/c that's annoying for tab-completion. So 'bs' it is.

I've moved all commands over; even though a case could be made that the "feeding" commands
(raise_exception, send_json, stress_test) are somewhat related to ingestion, that's not
a very good case :-)
2025-01-23 11:55:34 +01:00