Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move "migrate" script to its own process so it doesn't get loaded by main server #1125

Open
CarlosNZ opened this issue Sep 22, 2024 · 0 comments
Labels
Feature: improvement Improvement to existing feature Importance: Nice to have Issues that don't need to be included, just nice to have

Comments

@CarlosNZ
Copy link
Collaborator

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.

@CarlosNZ CarlosNZ added Feature: improvement Improvement to existing feature Importance: Nice to have Issues that don't need to be included, just nice to have labels Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: improvement Improvement to existing feature Importance: Nice to have Issues that don't need to be included, just nice to have
Projects
None yet
Development

No branches or pull requests

1 participant