Opened 4 years ago

Closed 4 years ago

#22032 closed Cleanup/optimization (fixed)

Document settings.MIGRATION_MODULES

Reported by: Baptiste Mispelon Owned by: gregchapple
Component: Documentation Version: master
Severity: Release blocker Keywords: migrations nlsprint14
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

There's no mention of this new setting in the documentation.

From what I understand, it's a way to override where Django can find migrations for a given app.

It's a dictionary where keys are the names of applications and the values are the name of the module (inside the app) where the migrations reside.

Change History (8)

comment:1 Changed 4 years ago by Marc Tamlyn

Severity: NormalRelease blocker

comment:3 Changed 4 years ago by Baptiste Mispelon

At the very least, it should be present in the full list of settings [1].

A mention in the migrations documentation itself would be a good idea too though I'm not sure which section is the most appropriate for that.

The second section ("Two commands") says that "the migration files for each app live in a “migrations” directory inside of that app [...]" so maybe a quick mention of the setting at this point would be best.

What do you think?

[1] https://docs.djangoproject.com/en/dev/ref/settings/

comment:4 Changed 4 years ago by gregchapple

Owner: changed from nobody to gregchapple
Status: newassigned

comment:5 Changed 4 years ago by gregchapple

Keywords: nlsprint14 added

comment:6 Changed 4 years ago by gregchapple

Added a patch in this pull request https://github.com/django/django/pull/2352

comment:7 Changed 4 years ago by gregchapple

Has patch: set

comment:8 Changed 4 years ago by Baptiste Mispelon <bmispelon@…>

Resolution: fixed
Status: assignedclosed

In ede99f0ec3a14e3ba218b53c51d4295dbef77e3e:

Fixed #22032 -- added documentation for settings.MIGRATION_MODULES

Note: See TracTickets for help on using tickets.
Back to Top