Skip to content
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

Publish migration #47

Closed
philipmclifton opened this issue Feb 13, 2022 · 5 comments · Fixed by #51
Closed

Publish migration #47

philipmclifton opened this issue Feb 13, 2022 · 5 comments · Fixed by #51

Comments

@philipmclifton
Copy link

Description:

Is it possible to publish the migration file?

@andrey-helldar
Copy link
Member

In general, yes, the usual copy operation. But why?

@philipmclifton
Copy link
Author

philipmclifton commented Feb 13, 2022 via email

@andrey-helldar
Copy link
Member

I understood what the problem is.

At the moment, the mechanism of this package uses the mechanism of migrations with some changes.

The peculiarity of migrations is that it does not create a table to create a table for storing migration statuses.

In the near future I will add the ability to automatically create a migration table when executing the art migrate command and its helpers.

@andrey-helldar
Copy link
Member

Have you tried php artisan migrate:actions:refresh command?

@andrey-helldar
Copy link
Member

@philipmclifton, I added a migrate:actions:fresh command to quickly restart actions on a clean base.

In case of rolling back migrations, the startup script can be one of the options:

php artisan migrate:fresh
php artisan migrate:actions:fresh
php artisan migrate:refresh
php artisan migrate:actions:fresh

The migrate:actions:fresh command released in version 2.8.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants