Rename main.php to ruckus.php about ruckusing-migrations HOT 6 CLOSED

I'm ok with just ruckus as long as the shebang resolves correctly. Will this pose issues on other platforms? If not and if its safe enough then we can truncate:

$ php main.php db:migrate

to

$ ruckus db:migrate

Then I say go for it.

from ruckusing-migrations.

the shebang mostly will resolve correctly in *nix. Now, if you installed your php in some unusual place, well you know it :), so you have to run it with your custom location /my/custom/path/php ruckus db:migrate.
In windows you will always use php ruckus db:migrate

from ruckusing-migrations.

after working with ./ruckus db:migrate, i think it's better to use php ruckus.php db:migrate

from ruckusing-migrations.

Using ./ruckus db:migrate you dont have to memorize the command. In console, you hit ./r [tab] and you get the command.

from ruckusing-migrations.

I too prefer a change of main.php to something more talking. Using composer it's dropping a main.php in my ./vendor/bin while all other commands have usefuller names there.

Personally I'd go for ruckus.php - for commands you'd have to use more often you simply can set up an shell alias (i.e. alias ruckus='/path/to/bin/php /path/to/bin/ruckus.php', so 'ruckus db:migrate' works fine; ...or even something shorter like alias r='/path/to/bin/php /path/to/bin/ruckus.php db:migrate')

from ruckusing-migrations.

I finally went for ruckus.php in #70 . And as @mplx said, you can play with alias to get your own flavor ;)

from ruckusing-migrations.