Move "migrate" script to its own process so it doesn't get loaded by main server #1125
Labels
Feature: improvement
Improvement to existing feature
Importance: Nice to have
Issues that don't need to be included, just nice to have
It's getting quite large now, and seems unreasonably to load a bunch of methods into memory that are only run at startup (and most not at all, if they're older migrations).
Suggest not calling "migrate" script from main server process. Instead, add it as a separate command in the the
yarn dev
script, to run it before the main server process.The text was updated successfully, but these errors were encountered: