Files
bugsink/.gitignore
Klaas van Schelven 5559fba754 Introduce FileEventStorage
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)
2025-02-12 17:11:24 +01:00

55 lines
610 B
Plaintext

# Python
*.pyc
__pycache__
# Virtual Environments / build
/.env
/.venv
/bin/
/include/
/lib/
/lib64
/pyvenv.cfg
/share/
/bugsink.egg-info/
/bugsink/_version.py
/dist/
# This matches the filestorage mentioned in development.py
/filestorage
# sqlite
/db.sqlite3
/db.*.sqlite3
/test.sqlite3
/db.sqlite3-wal
/db.*.sqlite3-wal
/test.sqlite3-wal
/db.sqlite3-shm
/db.*.sqlite3-shm
/test.sqlite3-shm
/snappea.sqlite3
/snappea.sqlite3-shm
/snappea.sqlite3-wal
# vim
*.swo
*.swp
# node (tailwind)
node_modules
/package*
# conf
/bugsink_conf.py
# static files
/collectedstatic
# Docker artifacts
/bugsink*tar