Peter Baumgartner

> Design a storage interface (an API) that enumerates, reads and writes PO files: the default implementation would use the local filesystem, exactly as it is done today. Django has...

> Not quite, by default Django only handles in local files, IIRC, but django-storages would be the perfect solution here, probably. Correct, when I said backends available, I was referring...

That makes sense. I've done some conversions from the Python file API to the Django file API in the past and the `open`, `read`, etc. are pretty easy/trivial to handle....

I dug into this a bit more and found the issue. If you are using [Redis' ACL](https://redis.io/topics/acl) to restrict a user to a specific key namespace, you can replicate the...

I stumbled on this while setting up a project with whitenoise. The workaround is to not use the [whitenoise storages](http://whitenoise.evans.io/en/stable/django.html#add-compression-and-caching-support). Instead, I used the setting: ``` STATICFILES_STORAGE = "django.contrib.staticfiles.storage.ManifestStaticFilesStorage" ```

#7269 may provide a workaround for this

Registering it in a Django AppConfig (or anywhere else in the standard Django import path) is problematic because of #121. I chose to build a custom management command for the...

@cyruszhang To use my solution, you'll need to create a custom management command: https://docs.djangoproject.com/en/dev/howto/custom-management-commands/ You would then run that command instead of `rqscheduler` as noted here, https://github.com/rq/rq-scheduler/issues/51#issuecomment-536652049

Just to clarify, my suggestion isn't that asdf is used to install the necessary packages. Instead that the `.tool-versions` file used by asdf could be used to determine providers and...

My 2¢, it should be lower on the priority list. `asdf` is primarily used for local development environments afaik. So, it can serve as a good hint about what to...