Why is there only a deployer.phar?

[flolanger]

In RC4, the whole project including bin/dep existed. Now since RC5 only the deployer.phar is available.

CI Pipelines using dep don't work any more because of that. Will this be available again in the future, or will this be the new standard?

Thanks in advance!

[antonmedv]

This is a way I decided to try. It was previously in deployer/dist package for a couple of years. Now I decided to merge it.

What kind of problem are you facing? Other classes not loading? Autolaod issues? This is work in process bug.

[flolanger]

I see, but can't you provide both? I think we are not the only one with this problem.

Would be great. Also, I think if dep isn't working anymore the whole docs need to be updated as well. Don't think that's worth it tbh.

[antonmedv]

I updated docs al.

[flolanger]

Can't you provide both? phar and source? So we can continue using deployer :)

[antonmedv]

You still can. Just create and alias. As in docs:

alias dep='vendor/bin/deployer.phar'

Replacing source with phar allows to drop composer requirements - no more conflicting packages.

[lsv]

Replacing source with phar allows to drop composer requirements - no more conflicting packages.

But isn't that just a bad excuse to not keep the requirements up to date?

Also its totally possible to use composer -d anotherdir require deployer/deployer

When you are working with phpstorm on windows, but in a WSL envorienment, deployer.phar, becomes deployer.phar.bat and then phpstorm can not auto complete anymore.

[antonmedv]

But isn't that just a bad excuse to not keep the requirements up to date?

Nope. There is dozens of project what depend on symfony 5 components.

becomes deployer.phar.bat and then phpstorm can not auto complete anymore.

Original phar still there In vendors dir. only bin dir has bat file.

[havvg]

I like this very much. I consider Deployer a tool, but a like it to be installed with the project rather than globally. The change regarding the .phar is nice, imho. In one of our smaller projects it reduces dependencies of the project massively.

$ composer require -w --dev deployer/deployer:^7.0@dev

Changelogs summary:

 - symfony/yaml removed (installed version was v5.2.5)

 - symfony/string removed (installed version was v5.2.6)

 - symfony/service-contracts removed (installed version was v2.4.0)

 - symfony/process removed (installed version was v5.2.4)

 - symfony/polyfill-php80 removed (installed version was v1.22.1)

 - symfony/polyfill-php73 removed (installed version was v1.22.1)

 - symfony/polyfill-intl-normalizer removed (installed version was v1.22.1)

 - symfony/polyfill-intl-grapheme removed (installed version was v1.22.1)

 - symfony/deprecation-contracts removed (installed version was v2.4.0)

 - symfony/console removed (installed version was v5.2.6)

 - psr/container removed (installed version was 1.1.1)

 - pimple/pimple removed (installed version was v3.4.0)

 - deployer/phar-update removed (installed version was v2.2.0)

 - deployer/deployer updated from v6.8.0 to v7.0.0-rc.8 major
   See changes: https://github.com/deployphp/deployer/compare/v6.8.0...v7.0.0-rc.8
   Release notes: https://github.com/deployphp/deployer/releases/tag/v7.0.0-rc.8

[dustingraham]

I'm still reading through issues and discussions but the problem I have is that phpStorm does not understand deployer.

I couldn't find anything in the documentation yet, but it would be nice if the files were available somewhere that phpStorm could index so that it could highlight and hint correctly.

[leevigraham]

@dustingraham Did you find a working solution for recipes?

[dustingraham]

@leevigraham No. I contacted phpstorm and they said it is not supported.

They only suggested suppressing it by adding to the previous line: /** @noinspection PhpIncludeInspection */

[antonmedv]

Other possibility:

import(recipes/laravel.php);

[leevigraham]

@dustingraham bummer… The click to go to file is the bit I really wanted.

[dustingraham]

@leevigraham Absolutely, me too.
@antonmedv That does get around the phpstorm error message, but doesn't solve the phpstorm IDE support. Thank you for the idea.