-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MIgrations #245
Comments
Anyone? |
I would appreciate a PR |
@serverfire would this be likely to get merged? |
@warksit sorry for late replay , Sure please send the pull request , thank you |
+1 for this improvement |
eafshary
added a commit
to eafshary/panel
that referenced
this issue
May 11, 2017
Close issue if solved please. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After running
php artisan migrate:refresh --seed
during development I then have to runphp artisan panel:install
to install the panel tables and thenphp artisan db:seed --class=PanelSeeder
which sets up my links. If the migrations were copied to the migrations folder they would then be included with the migrate:refresh command and I could then add PanelSeeder to DatabaseSeeder and refresh my database in a single command. Would you be interested in a pull request that updated the ServiceProvider and docs to do it this way instead?Now I have written this I see I can just copy them myself manually but think the above is the more 'standard' way of doing it. Actually you can't copy them as the autoloader doesn't like 2 classes of the same name.
The text was updated successfully, but these errors were encountered: