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
He ended up doing this to mitigate the effect of pushing all the static files through Django in a non-Debug deployment. It sounded like it was worth the effort.
The text was updated successfully, but these errors were encountered:
We don't have any custom static files in our backend app. What we do have is from DRF or Swagger and the big ones seem to be minified already. Some aren't (particularly the custom css), but seeing as how this only affects devs using the API and not the end users I'd give this a pretty low priority.
Would it make sense to do this to reduce either the number or the overall data load of all the files that come with Swagger?
I imagine that plain-Jane RESTful requests won't improve as a result of this effort, but would it make a foreseeable dent in the overall load or performance of the API container, if we expect any significant load of Swagger UI exploration?
He ended up doing this to mitigate the effect of pushing all the static files through Django in a non-Debug deployment. It sounded like it was worth the effort.
The text was updated successfully, but these errors were encountered: