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

Change the migrations default path. wouterj_eloquent.migration_path #80

Open
fabioars opened this issue Jan 11, 2018 · 4 comments
Open
Labels

Comments

@fabioars
Copy link

Hello,

I wan't do know, how do change the variable wouterj_eloquent.migration_path in my project.
If possible, use many paths I want.

image

tks!

@theofidry
Copy link
Contributor

You can simply override the parameter wouterj_eloquent.migration_path:

parameters:
    wouterj_eloquent.migration_path: 'my/path'

Although supporting multiple path won't be possible (and what's the use case?)

@fabioars
Copy link
Author

I'm trying to implement Porto SAP with Symfony 4.
Where all all MVC parts are separated by context.

@duayres
Copy link
Contributor

duayres commented Jan 11, 2018

Maybe if you separate it by use cases and another aggregation you want?
Ex: '2017_01_11_151700_Users_SomeAggregator_CreateUsersTable.php'
Correct if I'm wrong, but AFAIK migrations ever use to reside on a unique single path in various implementations.

@wouterj
Copy link
Owner

wouterj commented Jan 12, 2018

Hmm, in Laravel, you can call $migrator->path('my-custom-path'). However, you can't do that with my Bundle yet. I have to think of a nice way to configure all these classes in a Laravel-ish way (as #79 is about such feature as well).

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

No branches or pull requests

4 participants