An (optional) way to store the `event_data` (full event as JSON)
outside the DB. This is expected to be useful for larger setups,
because it gives you:
* A more portable database (e.g. backups); (depeding on event size
the impact on your DB is ~50x.
* Less worries about hitting "physical" limits (e.g. disk size, max
file size) for your DB.
Presumably (more testing will happen going forwards) it will:
* Speed up migrations (especially on sqlite, which does full table
copies)
* Speed up event ingestion(?)
Further improvements in this commit:
* `delete_with_limit` was removed; this removes one tie-in to MySQL/Sqlite
(See #21 for this bullet)
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.
I was missing package.json in git due to a too liberal .gitignore conf.
This botched tailwind when I restarted from a fresh git install
I never ran into this before b/c tailwind's npm stuff is only necessary during
development, not in e.g. localbugsink (because we checkin all outputs too)
