I have a question about storage objects in a migration enabled project.
I
have a project that uses a file system storage backend for storing
certain model FileFields, but the location is dependent on the
deployment and stored in the settings module. For example, for testing
locally I have the storage root pointed at a directory under my home
folder. Whenever I run makemigration, it tries to alter all the
FileFields to reflect whatever the current setting is, even though this
does not affect the database.
Is there a way to prevent the
storage parameter from getting serialized in the migration? If not, what
is a good way to handle storing files in different locations depending
on a configuration, without a bunch of unnecessary migrations?