Symfony CLI

[f-lawe]

Hello there,

I started a project locally using the Symfony image, I got surprised when I noticed that symfony is not the actual Symfony CLI tool, but is mapped to ./bin/console instead.

This tool allows useful operations, like running a dev server.

Is there a specific reason? Would you consider an update on that topic?

Thanks!

[shinsenter]

@f-lawe
Well, I think the reason the symfony command in the Docker images is not actually the Symfony CLI tool is that I did not know it existed as something separate from the Symfony framework.

When I created the Docker image for the Symfony framework, I thought it would be more useful and easier to remember to have a command named symfony instead of typing ./bin/console to run Symfony framework utilities, so I created it that way.

I will reconsider choosing another name for ./bin/console of the Symfony framework. As for the symfony command, I will leave it up to users to decide whether they want to install the Symfony CLI tool themselves and build their own Docker image based on mine.

[f-lawe]

Thanks for the quick reply!

Ok, that explains. Let me share the output of the Symfony CLI Tool:

Work on a project locally

  local:new                                                           Create a new Symfony project
  local:server:start                                                  Run a local web server
  local:server:stop                                                   Stop the local web server
  local:check:security                                                Check security issues in project dependencies
  composer                                                            Runs Composer without memory limit
  console                                                             Runs the Symfony Console (bin/console) for current project
  php, pecl, pear, php-fpm, php-cgi, php-config, phpdbg, phpize, pie  Runs the named binary using the configured PHP version

Manage a project on Cloud

  project:init              Initialize a new project using templates
  cloud:domain:list         Get a list of all domains
  cloud:environment:branch  Branch an environment
  cloud:environment:list    Get a list of environments
  cloud:environment:push    Push code to an environment
  cloud:environment:ssh     SSH to the current environment
  cloud:project:list        Get a list of all active projects
  cloud:tunnel:open         Open SSH tunnels to an app's relationships
  cloud:user:add            Add a user to the project
  cloud:variable:list       List variables

As you can see, it allows some interesting operations.

There is a already console shortcut mapped to ./bin/console in your dockerfile, so I don't think there is a need to find an other name. This one is very convenient, natural and useful in my opinion.

[f-lawe]

Whereas the CLI tool should be embed or not, that's up to you. It's meant for development purpose, so if the image is to be used on production, that's indeed not a good idea. I'm currently using shinsenter/symfony:dev-php8.4, so maybe installing that tool on dev images only would makes sense?