Closed alexhernandez closed 10 years ago
I agree there is a consensus on copying migrations to the app migrations folder, but Firewall does migrations is the old way Laravel folks were doing:
php artisan migrate --package=pragmarx/firewall
To undo it, you have to
php artisan migrate:rollback --package=pragmarx/firewall
Unfortunately refresh
will not work in this case.
And, still, I'm not sure it will work, I remember talking with Taylor about rollback not having the --package option...
So your best bet may be just delete all tables manually, since this is exactly what refresh will do for you.
I tried rollback
and your right it doesn't work. I get this error:
[RuntimeException]
The "--package" option does not exist.
What if i were to duplicate your migration file into my migration folder?
Call to undefined method PragmaRX\\Firewall\\Vendor\\Laravel\\Facade::down()
Seems to be the issue.
It should work. Comment the Firewall alias in your app/config/app.php, looks like PHP was also refering to the wrong class when trying to run the migration.
As soon as I get some time here I'll change the way it does migrations.
muito obrigado
De nada. :)
I just pushed a new way of doing migrations. Check the readme, please.
Sounds good. Thanks.
Just tested it, it works. Thanks.
One thing you forgot was to add firewall:tables
to your docs instead of tracker:tables
Fixed. Thanks.
When using firewall if I run:
I get a Symfony error. My guess is because firewall doesn't keep its migration file inside laravels migration folder, but instead inside its own vendor folder.
Any idea how I can get this to work?