Rename main.php to ruckus.php

[salimane]

I think It's better to give main.php some identification. When deploying it with some other scripts, main.php doesn't tell immediately what this script is for. Renaming it to :

1 - ruckus with the shebang #!/usr/bin/env php at the top of the script
2 - ruckus.php

I think ruckus is the best but ruckus.php is also ok, at least it's better than main.php

What do you think ?

[ruckus]

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.

[salimane]

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

[salimane]

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

[akDeveloper]

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

[mplx]

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')

[salimane]

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