Removing default migrations from Laravel

Question

After creating a new Laravel project with laravel new, there are a couple of migration files in the database > migrations folder:

2014_10_12_000000_create_users_table.php
2014_10_12_100000_create_password_resets_table.php

These seem to be examples of typically useful migrations and are probably a good place to start if you need a system that requires something similar. However I'd like to delete them so they don't clash with something in a new project I'm building.

I was hoping I would be just able to delete the files, as I've not run php artisan migrate yet, but when I try my IDE says:

Why are these files already tied into the system, and how can I safely remove them? Is there some documentation on the Laravel site that I've not been able to find about this?

I guess I could ignore the warning and try running composer dump-autoload -o, but is this really OK?

If you haven't ran you migrations yet you are safe to delete them. Ignore your IDE. — Marwelln, May 19 '17 at 16:16

score 5 · Accepted Answer · answered May 19 '17 at 16:43

5

Why are these files already tied into the system

to map all project classes

how can I safely remove them?

Ignore IDE and delete them then run composer dump-autoload and will remap project classes

Is there some documentation on the Laravel site that I've not been able to find about this?

i don't see any thing about this in laravel documentation site

answered May 19 '17 at 16:43

Mortada Jafar

3,529
1
18
33

1

Sweet. That worked. All references from the code were removed. Thanks! – Chuck Le Butt May 19 '17 at 16:56

score 2 · Answer 2 · answered May 19 '17 at 16:42

2

Ignore the warnings and delete them. The migrations that come out of the box are to help you get started with basic auth. You don't necessarily need them. Run composer dump-autoload when you're done.

answered May 19 '17 at 16:42

Sandeesh

11,486
3
31
42

Removing default migrations from Laravel

2 Answers2