PHP8 Support

[antonmedv]

Current stable version v6.8.0 does not support PHP8 due to next facts:

• composer.json restriction on ~7.0
• requirement of Symfony components also lacks PHP8 support
• deployphp/recipes also require ~7.0
• possible unknown backward incompatibility with php8.

Solutions to this problem:

Upgrade to Deployer v7.

• Currently in beta
• Upgrade docs are here:
  https://github.com/deployphp/deployer/blob/master/docs/UPGRADE.md#upgrade-from-6x-to-7x
• Best possible solution, but requires some time.

Switch to deployer/dist

• https://github.com/deployphp/distribution
• This is phar version of dep tool. Everything will work same.

Solution for deployphp/recipes

• Just copy paste needed recipes.

[ROTGP]

I have been using v6.8 with PHP7.4 and I've been very happy with it, but now that I'm required to use PHP 8 I'm afraid that I'll have to look for another solution.

As for the beta version being the "Best possible solution" - I've already lost a couple of days trying to make this work, and with no success. The "upgrade guide" is vague and confusing ("Change hostname to alias", and then "alias() is deleted, host() itself sets alias" - what?). Things that were working well before are breaking (the 'cleanup' task, rsync in general, recipe integration, etc).

It would be extremely helpful to provide some examples of common usage for v7, especially for using the rsync recipe.

Thanks for your work and I hope that you manage to get v7 sorted out - I really love deployer.

[ROTGP]

@staabm I ended up opting for a simpler deployment strategy with fewer dependencies - this package has been great but in the end PHP8 has been out for 4 months and having to mess around with trying to integrate the (unstable) beta version into my github-action workflow was a nightmare. Now I'm using this SSH action combined with shell scripting which I find faster, with fewer dependencies, and more flexible.

[antonmedv]

If you like yaml more:

name: remote ssh command
on: [push]
jobs:

  build:
    name: Build
    runs-on: ubuntu-latest
    steps:
    - name: executing remote ssh commands using password
      uses: appleboy/ssh-action@master
      with:
        host: ${{ secrets.HOST }}
        username: ${{ secrets.USERNAME }}
        password: ${{ secrets.PASSWORD }}
        port: ${{ secrets.PORT }}
        script: whoami

Than PHP:

task('build', function () {
    run('whoami');
});

😄

[ROTGP]

@antonmedv not meaning any disrespect - but your previous comment is not really accurate (at least, not in my experience). For me it has been more like:

1. composer require deployer/deployer
2. ./vendor/bin/dep init
3. configure a whole lot of stuff in deploy.php
4. wrestle with recipes and try to understand why they’re not working
5. upgrade to PHP 8 (as it’s been out for 4 months now) and realize that deployer is incompatible, so composer install is broken and the project no longer builds
6. try to get the unstable beta version working, only to realize that the API has changed completely and furthermore is undocumented
7. end up with a broken project that can’t be built or deployed and having to downgrade to an older version of PHP

Honestly I prefer the yaml approach of using Github Actions to SSH into the server and execute a shell script. It adds no dependencies to the project itself, it’s more flexible, transparent, customizable, and maintainable 😄

[antonmedv]

Yeah, process of migration is bumpy. Apologies for it, I was trying my best.

FYI, Deployer v7 has yaml recipe supports as well 😁

[ROTGP]

I look forward to checking out v7 when it becomes available - the yaml recipe sounds promising 👍🏻

[m1roff]

What is replacement for Deployer::getCalledScript()?

[mmenguy-vu]

Hello,
Any news for the release date fo PHP8 support?
Thanks