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

What's the best practice for adding db-migrate to a project with an existing database? #828

Open
1 of 3 tasks
murderteeth opened this issue Dec 21, 2023 · 0 comments
Open
1 of 3 tasks

Comments

@murderteeth
Copy link

murderteeth commented Dec 21, 2023

I'm submitting a...

  • Bug report
  • Feature request
  • Question

Current behavior

db-migrate works great if you're greenfielding a new project. but my project is already live and has a database with existing schema and data. what's the recommended approach for adding db-migrate to this project?

related #604 (comment)

Expected behavior

I expect clear guidance\docs on integrating db-migrate with live projects that already have schema and data. Alternatively, I expect that if db-migrate isn't suitable for projects that already have schema and data, the docs\README make that clear instead.

Minimal reproduction of the problem with instructions

NA

What is the motivation / use case for changing the behavior?

NA

Environment


db-migrate version: latest

Additional information:
- Node version: LTS
- Platform:  linux

Others:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant