Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • thanks for the answer. But I don't understand, when I modify the migrations php file which is auto create by laravel, drop all the "email" columns. and run the php artisan make:auth. I also get the email relate files, such as some blade.php file . Does it mean I should remove all the email things just auto genreate after run the make:auth command, ? Commented May 12, 2016 at 3:04
  • No, what you need to do is after you remove the unique key from your migration file, you can go to terminal and type in php artisan migrate:refresh and it will refresh the database with the new migration. You don't need to do php artisan make:auth again as it just generates the routes and the views. Your migration file is not generated by that command. Commented May 12, 2016 at 3:11