We intended on using this package for one of our main applications, but we need seeders to run in all environments and it seems like the logic currently limits seeders to a specific environment. This makes it difficult for us to populate all of our environments with the seeded data without duplicating code. Is there something in the documentation I'm missing that allows us to have "global" seeders?

really nice package really easy way to create, run, install seeds i have check the code seeds path is define in config, can you add an option in package of providing path of the seed desire location, if that path options is not available then it can take config path. this will help other package developers to create new commands for creating seeds on other location they will call your commands with in their package commands no need to reinvent the wheel again,

This package is a great idea, but I am having issues getting it to work with production files.

With the --env=production option, the package creates a seed file in the smartSeeds/production directory. However when I use the seed:run command, it does not find the file.

Based on what I am seeing it is looking for the file in the root directory.

/app/database/smartSeeds/someSeeder.php

I even tried running the command like so seed:make --env=production but it's the same result.

Anyone else experiencing this? Any suggestions?

By default, the seed:run command runs all the seed classes.

However, it would be useful to be able to use the --class option to specify a specific seeder class to run individually. Much like the functionality provided by Laravel's out of the box seeding.

This could look something like:

php artisan seed:run --class=UserSeeder

or

php artisan seed:run --class=seed_2015_06_23_002940_UserSeeder

A seeder file generated for the stub still has backslash in the name space like namespace App\; which is invalid. I made the rtrim() strip the backslash instead which remove the last backslash. This fixed my issue.

Use can specify php artisan seed:make --path={path from base_path()} to have their seed file created in that location. In the process, it will also create any intermediary folder along the way.

Add checking for the environment to the SeedMigrator.

I had to do a few funny things to get this to work so it's more of a proof-of-concept. As it stands, the seed:make command will still generate a seeder that is namespaced. However, it won't be able to run with seed:run command until the user remove the namespace. Please do not approve this pull request as is.

I was having problem getting it to migrate files in the folders named after the environment. It seems pretty straight forward in the resolve() function of the migrator. However, it turns out the runUp() wasn't using resolve() method neither did the discovering and invoking the seeder processes.

When I tried to implement it on top of the namespace functionality, I was getting errors with it not being able to find the file. I decided to make as little change to the code as possible so I remove the namespacing from my seeders and that allows this code to work. It seems like the namespacing wasn't fully implemented yet and it was non-trivial to get going.

Other things that I've explored:

1. in getMigrationFiles(), I tried to preserved the environment name hoping that I wouldn't have to overwrite the requireFiles() function. That broke the instantiation of the class in migrator->resolve()
2. I tried to resolved the file path the the environment in the seed commands rather than migrator but that also causes problem with the environment name being used as class name and wouldn't allow me to discover both files outside of the environment folder and inside of it. For example, it would be nice if both of the following files are loaded if local environment was specified.

/database/smartSeeds/seeder_2015_01_01_vendors.php
/database/smartSeeds/local/seeder_2015_01_01_vendors.php

1. I wasn't able to instantiate the seeder with namespace for some reason. I'm not sure if there is something going on with the autoloader. In any case, it doesn't seem like Laravel's migration files generated has namespaces anyway so I'm not really sure what the intentions of supporting the namespace are. I'm leaving that up to you.

Thanks!

Hi,

first of all big thank you for that package, this is what I'm looking for, but I see that after runing rollback nothink was changed in my db, the data is the same as before. So maybe seed classes should have two methods up and down like migrations has, so the developer can write what will happen when data is pushing to and pulling from db?

When I run php artisan migrate:refresh --seed the second time then integrity constraint violations are thrown because the data still exists in db even if I run seed:rollback or seed:reset

Is there any solution for that problem?

This will fix the problems during the compsoer setup cause it just requiers any 5.* version and not a special 5.0.* one. Laravel tries to replace all the illuminate packages with it's self.version and this creates the confilcts.

In Laravel 5, the database-related files have been moved to /database from the base path rather than in /app/database folder. Switch the seed migrator to look in the database file using database_path() as the base and change the config file to just smartSeeds instead.

I'm creating a seeder this way:

php artisan seed:make test --env=sprint-7

but when I run:

php artisan seed:run --env=sprint-7

I get the following error:

[Symfony\Component\Debug\Exception\FatalErrorException] Illuminate\Filesystem\Filesystem::requireOnce(): Failed opening required '/vagrant/database/smartSeeds/seed_2016_12_31_0_PagesTableSeeder.php' (include_path='.:/usr/share/php:/usr/share/pear')

ps. I'm using the env parameter as a version instead of the real environment.

Add checking for the environment to the SeedMigrator.

I had to do a few funny things to get this to work so it's more of a proof-of-concept. As it stands, the seed:make command will still generate a seeder that is namespaced. However, it won't be able to run with seed:run command until the user remove the namespace. Please do not approve this pull request as is.

I was having problem getting it to migrate files in the folders named after the environment. It seems pretty straight forward in the resolve() function of the migrator. However, it turns out the runUp() wasn't using resolve() method neither did the discovering and invoking the seeder processes.

When I tried to implement it on top of the namespace functionality, I was getting errors with it not being able to find the file. I decided to make as little change to the code as possible so I remove the namespacing from my seeders and that allows this code to work. It seems like the namespacing wasn't fully implemented yet and it was non-trivial to get going.

Other things that I've explored:

1. in getMigrationFiles(), I tried to preserved the environment name hoping that I wouldn't have to overwrite the requireFiles() function. That broke the instantiation of the class in migrator->resolve()
2. I tried to resolved the file path the the environment in the seed commands rather than migrator but that also causes problem with the environment name being used as class name and wouldn't allow me to discover both files outside of the environment folder and inside of it. For example, it would be nice if both of the following files are loaded if local environment was specified.

/database/smartSeeds/seeder_2015_01_01_vendors.php
/database/smartSeeds/local/seeder_2015_01_01_vendors.php

1. I wasn't able to instantiate the seeder with namespace for some reason. I'm not sure if there is something going on with the autoloader. In any case, it doesn't seem like Laravel's migration files generated has namespaces anyway so I'm not really sure what the intentions of supporting the namespace are. I'm leaving that up to you.

Thanks!