deployphp / distribution Goto Github PK

Now we have 3 types of installing deployer. What about vendoring symfony packages inside deployer repo?

No deps in deployer/deployer package, and symfony under src/Vendor/Symfony.

What do you think?

Despite being released 11 days ago, Deployer 7.0.0-beta.2 is not available here.

Can you publish Deployer 6.4.2?
Thanks

hello

seems like there is no distribution for Deployer 6.5.0.
Tnx.

What about merging them together?

After installing this package via composer, I see the following files in vendor/deplyer/dist directory:

composer.json dep .gitignore README.md update

The only file that we actually need is dep.
Other files should be removed (added to "export-ignore" in .gitattributes?)

Composer version 2.0.7
PHP 8.0.16

Looks like the deployer.phar file is not being downloaded when installing the latest version.

Using "deployer/dist": "v7.0.0-rc.3" works like a charm.

Any suggestions?

Any chance to release 6.1.0 version?

Using (via composer) deployer/dist:^6.8 and PHP 8.1 results into:

those deprecation logs. I assume PHP 8(.1) is supported? dep deploy e.g. works just fine

Upgrade without issues from v6.8 to v7.0.0-rc.4 with PHP 8.1.3 but I've noticed that the following snippet:

// Main
task('deploy', [
    'deploy:info',
    'deploy:prepare',
    'deploy:lock',
    'deploy:release',
    'deploy:update_code',
    'deploy:unlock',
    'deploy:shared',
    'deploy:vendors',
    'deploy:symlink',
    'typo3:finish',
    'deploy:unlock',
    'deploy:cleanup',
])->desc('Deploy your project');

Is being ignored by deployer and it executes instead the following commands:

And runs into a locked-state. Note that right after update_code it should actually "force" unlock - testing purpose since I was wondering why I kept run into a locked state.

Any ideas to this?

What do you think about adding replace to composer.json?

replace: {
  "deployer/deployer": "self.version"
}

Then it's possible to install additional packages that require Deployer, but still use deployer/dist in a project while avoiding dependency conflicts.

Installing 7.0.0 RC3 on Windows 10 and PHP 7.4, when I execute I get:

λ .\vendor\bin\dep.bat
PHP Fatal error:  Namespace declaration statement has to be the very first statement or after any declare call in the script in D:\projects\example\vendor\bin\dep on line 13

Fatal error: Namespace declaration statement has to be the very first statement or after any declare call in the script in D:\projects\example\vendor\bin\dep on line 13

When I take a look at vendor\bin\dep, the namespace declaration is the first statement.

Invoking dep yields a PHP warning:

$ dep --help
PHP Warning:  Constant  already defined in /.../vendor/deployer/dist/dep on line 5

Warning: Constant  already defined in /.../vendor/deployer/dist/dep on line 5
Description:
  List commands

Usage:
...

This issue does not occur with deployer/deployer.

Environment:

$ php --version
PHP 8.0.14 (cli) (built: Dec 20 2021 21:22:57) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.14, Copyright (c) Zend Technologies
    with Zend OPcache v8.0.14, Copyright (c), by Zend Technologies

The latest 4.x releases are not present in this repository. Could you please add new dist packages for them, at least for the latest version?

rc3 does not when imported into a project

$ composer dep deploy prod
> dep 'deploy' 'prod'
Script dep handling the dep event returned with error code 255

Unfortunately I can't use rc4 either as it has another bug:

$ composer dep deploy prod
> dep 'deploy' 'prod'
task deploy:info                                                                                               
[prod] info deploying develop
task deploy:setup
task deploy:lock
task deploy:release
task deploy:update_code
[prod]  error  in update_code.php on line 84:
[prod] run export GIT_TERMINAL_PROMPT='0' GIT_SSH_COMMAND='ssh -o StrictHostKeyChecking=accept-new'; cd ~/application/prod/.dep/repo && (/usr/local/cpanel/3rdparty/lib/path-bin/git remote update 2>&1)
[prod] Fetching origin
[prod] command-line line 0: unsupported option "accept-new".
[prod] fatal: Could not read from remote repository.
[prod] Please make sure you have the correct access rights
[prod] and the repository exists.
[prod] error: Could not fetch origin
[prod] exit code 1 (General error)
task deploy:failed
task deploy:unlock
Script dep handling the dep event returned with error code 1

I'm working on a package with custom recipes and would like to use phpstan, but it dosen't work, because the distribution file has no extension.

The following config works with phpstan when I rename dep to dep.phar.

parameters:
    bootstrapFiles:
        - phar://vendor/deployer/dist/dep.phar/vendor/autoload.php

Would it be possible keep the extension in the distribution and to add a symlink to keep backward compatibility?