Where to put migration within a Laravel 5.1 package?

Question

Well, I do have a package take I only use alongside with my system. I do have migrations for that package (it was build on Laravel 4.2, and I'm upgrading it).

That being said: On my package (former workbench) on Laravel 5.1, where do I put and how do I run my migrations?

Does any of you guys know how to deal with this?

UPDATE:

This is not the case of a simple migration. Back on laravel 4.*, we were able to maintain migrations for each package (if it was so desirable), and I do have some migrations been held by my own package, in it's own database, with it's own table. So... I need it to be a PACKAGE's migrations and not a ROOT INSTALATION's migration.

I think I did! (I was sure I did till you pointed it out... now I'm scared to ensure!) — Dennis Braga, Nov 23 '15 at 14:35
Both! But, I already have them. Just want to run, or further more, create. — Dennis Braga, Nov 23 '15 at 14:40
just put them in `/database/migrations` to run, in command prompt type `php artisan migrate` (in your root project). note: you might need to tune your code a little. — Bagus Tesa, Nov 23 '15 at 14:41
.... ok, but I needed not to be a root system's migration, but a package's migration instead. — Dennis Braga, Nov 23 '15 at 14:43
package should go into `/vendor` - wait, did you install it using composer or manually? well, i'm starting to wonder, is it possible for [package](http://laravel.com/docs/5.1/packages) having it's own migrations? — Bagus Tesa, Nov 23 '15 at 14:44
I think it does... http://laravel.com/docs/5.1/packages#publishing-file-groups — Dennis Braga, Nov 23 '15 at 15:06
and yes, `vendor:publish` just copy views to `/views` and migrations to `/database/migrations` - thus, after being published, we still need to run `php artisan migrate`. in the end, it just like put them in migrations folder. am i wrong? — Bagus Tesa, Nov 23 '15 at 15:21

score 4 · Accepted Answer · answered Oct 12 '17 at 16:04

4

You can put it in packages/.../src/migrations. To run it:

You can insert in composer.json :

"autoload": { "classmap": [ "database", "packages/.../src/migrations" ],

Or just call :
- Laravel 4.x php artisan migrate --package="{vendor}/{name}"
- Laravel 5.x php artisan migrate --path=/packages/.../migrations

For more info : check this blog from websanova.com

answered Oct 12 '17 at 16:04

4givN

2,936
2
22
51

I accidentally upvoted this answer even though it didn't work for me. This other one did: https://stackoverflow.com/a/50499101/470749 – Ryan May 24 '18 at 00:06

score 2 · Answer 2 · answered May 24 '18 at 00:05

Updated Answer for Laravel 5.6+

https://laravel.com/docs/5.6/packages#migrations says:

If your package contains database migrations, you may use the loadMigrationsFrom method to inform Laravel how to load them. The loadMigrationsFrom method accepts the path to your package's migrations as its only argument:

/**
 * Perform post-registration booting of services.
 *
 * @return void
 */
public function boot()
{
    $this->loadMigrationsFrom(__DIR__.'/path/to/migrations');
}

Once your package's migrations have been registered, they will automatically be run when the php artisan migrate command is executed. You do not need to export them to the application's main database/migrations directory.

The forward-slash is important. In my case, I used: $this->loadMigrationsFrom(__DIR__ . "/migrations");.

smartrahat · Answer 3 · 2015-11-25T10:35:22.447

-1

To create a migration:

Go to command prompt locate your project root folder and run this command: php artisan make:migration yourMigrationFileName --create=tableName
You can found your migration file in yourProjectFolder\database\migrations\timestamp_yourMigrationFileName.php
Create your table.

To run the migration:

Go to command prompt locate your project root folder and run this command: php artisan migrate

And don't forget to declare your table name in your Model. You can do it by writing protected $table = 'tableName' in your model.

edited Nov 25 '15 at 10:35

answered Nov 23 '15 at 14:50

smartrahat

5,381
6
47
68

to be precise, it's not some date, it's timestamp. – Bagus Tesa Nov 23 '15 at 15:21
@Tezla I am sorry for that, but this is not the issue. The timestamp will created by Laravel itself. – smartrahat Nov 23 '15 at 15:29
This is just a standart migration. Of that I read on the docs. – Dennis Braga Nov 23 '15 at 18:19

Where to put migration within a Laravel 5.1 package?

3 Answers3

Updated Answer for Laravel 5.6+

Linked