Skip to content

Separate init step for migrations shouldn't be necessary #46

@bmtcril

Description

@bmtcril

The code here introduces separate tutor ... do init steps for running Django migrations for the sample plugin. This shouldn't be necessary since the plugin is installed with the rest of the Django dependencies which get picked up and migrated automatically.

Not critical, but maybe confusing, and definitely slows init down by 30+ seconds to spin up the container and run the whole no-op migration path.

# ---------------------------------------------------------------------------
# Migrations: Run openedx_plugin_sample migrations on init
# ---------------------------------------------------------------------------
hooks.Filters.CLI_DO_INIT_TASKS.add_item((
"lms",
"./manage.py lms migrate openedx_plugin_sample",
))
hooks.Filters.CLI_DO_INIT_TASKS.add_item((
"cms",
"./manage.py cms migrate openedx_plugin_sample",
))

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions