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

[Proposal/Enhancement] Artisan CLI Migrate command does not go through all sub folders of the migrations folder. #2561

Closed
Xees opened this Issue Oct 26, 2013 · 7 comments

Comments

Projects
None yet
6 participants
@Xees

Xees commented Oct 26, 2013

I have a massive project with over ~130 migrations. And i have them sorted into 4 sub folders inside the migrations folder.

Yet when i migrate using artisan. It only sorts through the base migrations folder and not its subfolders.

I think this is a useful enhancement for large projects.

@crynobone

This comment has been minimized.

Contributor

crynobone commented Oct 26, 2013

You should be able to do (right away):

php artisan migrate --path=/app/database/migrations/foo1
php artisan migrate --path=/app/database/migrations/foo2
php artisan migrate --path=/app/database/migrations/foo3
@Xees

This comment has been minimized.

Xees commented Oct 26, 2013

Why limit the user to using commands for each subfolder when you can make artisan migrate all subfolders automatically?

@crynobone

This comment has been minimized.

Contributor

crynobone commented Oct 26, 2013

I'm saying that what you can do right now, and you can also swap the implementation based on your own project.

Otherwise just hope there a significant request support your request for @taylorotwell to spend his time working on it 😄

@mikerogne

This comment has been minimized.

mikerogne commented Oct 26, 2013

👎 I see no reason for this.

@robclancy

This comment has been minimized.

Contributor

robclancy commented Oct 26, 2013

Unneeded over complication on a nice and simple system that works nicely

@ShawnMcCool

This comment has been minimized.

Contributor

ShawnMcCool commented Oct 26, 2013

Migrations are essentially a sequential line. I'm guessing that someone is bending the migrations system to fit an alternate need. Perhaps creating a solution directly targeted for that need would be better? You could still use Schema and everything.

@taylorotwell

This comment has been minimized.

Member

taylorotwell commented Oct 28, 2013

Nested migration folders not needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment