If its only a command line app, you do not need the entire Laravel install. If you want it to work in a different Laravel app, make a Laravel package. If you just want a command line app, use the Symfony console component. You could even extract the Laravel console classes out to your app and wrap up the Symfony classes to make it a little easier to use.

1 like

rahul286

9 years ago

Level 3

@zachleigh thanks for the answer.

We started as a command line app only and even explored the possibility of using Symfony/console.

As you have already guessed, Artisan (Laravel Console) is much easier to use, and I found packages such as https://github.com/moon0326/artisan which extracts Laravels console classes.

But as your application is growing we need a lot more stuff such as ORM, migrations, task scheduling, job queue and also RESTful API.

Earlier we thought we would use Symfony with different components, but when we started listing everything we need, Laravel seemed to have a lot many things in one place.

You may like to have a look at relevant issue for the list I am talking - https://github.com/EasyEngine/easyengine/issues/858

How would you have chosen between Laravel and Symfony console for a big command-line app?

Thanks again.

zachleigh

9 years ago

Best Answer

Level 47

@rahul286 I think in your case, Laravel makes a lot of sense, especially if you're planning on adding an api and web interface. Glad you found a solution!

1 like

rahul286

9 years ago

Level 3

Thanks. you solved my another problem. :-)

I was concerned about starting with Laravel and instead was planning to use:

Symfony/console for command-line-app
Lumen or Slim for REST API
Laravel for web interface

But as command line app contains all features I felt a single Laravel app would make more sense.

Please or to participate in this conversation.