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

Update README instruction for engines path support #346

Merged
merged 2 commits into from
Oct 9, 2024

Conversation

gtrias
Copy link
Contributor

@gtrias gtrias commented Oct 9, 2024

Since last version, support for Rails multi-engine setup has been included. However the README don't include instructions on how to configure it.

Additionally, we have never been able to make this feature work with the old "Rails Engines support" section instructions.

In this PR I propose to change this section for instructions on how to actually use the multiple data_migrations_path approach to get the same results with additional simplicity (you don't need to modify your engines initializers)

Since last version, support for Rails multi-engine setup has been included. However the README don't include instructions on how to configure it.

Additionally, we have never been able to make this feature work with the old "Rails Engines support" section instructions.

In this PR I propose to change this section for instructions on how to actually use the multiple `data_migrations_path` approach to get the same results with additional simplicity (you don't need to modify your engines initializers)
@vprigent vprigent merged commit dbc2d5d into ilyakatz:main Oct 9, 2024
15 checks passed
vprigent pushed a commit to vprigent/data-migrate that referenced this pull request Nov 9, 2024
* Update README instruction for engines path support

Since last version, support for Rails multi-engine setup has been included. However the README don't include instructions on how to configure it.

Additionally, we have never been able to make this feature work with the old "Rails Engines support" section instructions.

In this PR I propose to change this section for instructions on how to actually use the multiple `data_migrations_path` approach to get the same results with additional simplicity (you don't need to modify your engines initializers)

* Keep previous folder name
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

Successfully merging this pull request may close these issues.

2 participants