You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would make sense to me that the file storage class could be selected as a configuration, especially since many deployments these day are on ephemeral file systems.
We could set storage, something like this (untested):
from django.core.files.storage import get_storage_class
from django.conf import settings
storage_class = getattr(settings, 'SILKY_STORAGE_CLASS', 'silk.models.ProfilerResultStorage')
silky_storage = get_storage_class(storage_class)()
class Request(models.Model):
# [...]
prof_file = FileField(null=True, storage=silky_storage)
The text was updated successfully, but these errors were encountered:
It would make sense to me that the file storage class could be selected as a configuration, especially since many deployments these day are on ephemeral file systems.
We could set
storage
, something like this (untested):The text was updated successfully, but these errors were encountered: