It seems impossible make table structure changes the way migration is setup about nova-blogify-tool

[MattMangoni]

I know, that's something I always wanted to change. Probably going to switch to the default migration System :)

[MattMangoni]

@moleculezz Okay, so, I'm rebuilding everything from scratch.
The result wasn't good enough imho.

I'll try to keep things simpler and to control each PR closely.
I don't want things to break or to become too complex.

If you want to contribute, you can find the code (still in early development) inside the "new" repo :)

[moleculezz]

@MattMangoni I've been working on something locally. But it drops the entire dashboard that installs the DB tables.
It uses the default php artisan migration.

I personally find it easier to let the scripts take care of installing it instead of manually going through the Nova Admin and clicking install. Also I rather not have that for users to see in the Nova Admin.

I didn't want to submit it since I didn't know if you wanted to drop that feature. But I can submit it if you're interested.

[MattMangoni]

@moleculezz I don't know, I just didn't want people to have some tables created without even being notified about it :(

[moleculezz]

@moleculezz I don't know, I just didn't want people to have some tables created without even being notified about it :(

This is exactly what Laravel, most Laravel packages and Laravel Nova does for you.

But I understand your point of view. You are looking at it from a CMS user point of view.
In my opinion Laravel Nova was made with the developer in mind. So that's why most things are coded and don't have a UI to click through. It's made for easy deployment.

But hey, it's your package, and that's exactly why I did not submit the PR. I understood you were doing something different.

[MattMangoni]

@moleculezz just tweaked stuff a little bit. I didn't understand your point completely

http://prntscr.com/ky5mf0

[moleculezz]

That's nice. Instead of executing it from the UI, you just check for the status.