Tool based on deployer.org to perform zero downtime deployments of Magento 2 projects

Last update: Apr 28, 2022

Magento 2 Deployer Plus

Build Status

  • Reliable fully-automated deployments tool for Magento 2.
  • Zero downtime deployments on Magento versions >= 2.2
  • Automating your deployments is as easy as defining the servers where you want to deploy to.

Motivation

This project aims to offer a common solution for fully-automated deployments on all versions of Magento 2. This tool uses the well known Deployer and adds specific recipes for each Magento 2 version.

Important Features

  • Deployer code syntax
  • Super easy setup
  • Deploy to multiple servers
  • Zero Downtime (only Magento >= 2.2)
  • Build and Deploy artifacts (only Magento >= 2.2)
  • Secure rollbacks (only Magento >= 2.2)

Installation

composer require "jalogut/magento2-deployer-plus"

Setup

Magento >= 2.1

cp <vendor_dir>/jalogut/magento2-deployer-plus/deploy.php.sample_2_1 deploy.php

Magento >= 2.2

cp <vendor_dir>/jalogut/magento2-deployer-plus/deploy.php.sample_2_2 deploy.php

Magento >= 2.2.5

cp <vendor_dir>/jalogut/magento2-deployer-plus/deploy.php.sample_2_2_5 deploy.php

Usage

Git deploys:

<bin_dir>/dep deploy [<stage>]

Build artifact deploys: (only Magento >= 2.2)

<bin_dir>/dep build
<bin_dir>/dep deploy-artifact [<stage>]

Disclaimer

Build command

Build command can only be used if config propagation is properly configured. See Magento DevDocs:

Also check app:config:dump issue and workaround here:

Troubleshooting

Js translations missing (magento versions >=2.1.3 <2.2.1)

  • Problem: Known Magento issue when executing setup:static-content:deploy for several languages.

  • Github Issues:

  • Solution: Until that gets fixed in 2.2.1, the only workaround is to execute setup:static-content:deploy individually for each language:

     // deploy.php
     task('files:static_assets', '
     	{{bin/php}} {{magento_bin}} setup:static-content:deploy en_US {{static_deploy_options}}
     	{{bin/php}} {{magento_bin}} setup:static-content:deploy de_CH {{static_deploy_options}}
     	{{bin/php}} {{magento_bin}} setup:static-content:deploy fr_FR {{static_deploy_options}}
     ');

Compilation error

  • Solution: Increase php memory_limit configuration to 728M o 1024M

Static deploy error when setting a new template (if config propagation is not used)

  • Problems:

    • [LogicException] Unable to load theme by specified key: 'Template'
    • @variable is undefined in file
  • Reason: If a new template is set, running setup:upgrade is required before executing setup:static-content:deploy

  • Solution: Skip setup:static-content:deploy first time you deploy the new template:

    1. Temporary disable task files:static_assets

      // deploy.php
      task('files:static_assets')->onRoles('Skip');
      
    2. Perform a new release

    3. Enable back files:static_assets on your deploy.php file

      • Remove task('files:static_assets')->onRoles('Skip');
    4. Manually execute files:static_assets

      <bin_dir>/dep files:static_assets [<stage>]
      

    After that, future deployments will work without issues

Prerequisites

  • PHP >= 7.0.8
  • MAGENTO >= 2.1

ChangeLog

CHANGELOG.md

Developers

Licence

GNU General Public License, version 3 (GPLv3)

Copyright

(c) Juan Alonso [email protected]

GitHub

https://github.com/jalogut/magento2-deployer-plus
Comments
  • 1. setup:db:status -> No information is available: the Magento application is not installed.

    Here's what am trying to do:

    • I have two seperate magento2.2.7 instances on the same server
    • One am using as my dev instance and other one as staging
    • I installed the deployment tool on my dev instance, so that what ever changes I make on my dev instance i'd be able to deploy it on my staging server

    Here's what I did

    1. composer require "jalogut/magento2-deployer-plus"
    2. cp vendor/jalogut/magento2-deployer-plus/deploy.php.sample_2_2_5 deploy.php ( as am using 2.2.7 version of Magento )

    That's how my deploy.php looks like

    <?php
    
    namespace Deployer;
    
    require 'vendor/jalogut/magento2-deployer-plus/recipe/magento_2_2_5.php';
    
    // Use timestamp for release name
    set('release_name', function () {
        return date('YmdHis');
    });
    
    // Magento dir into the project root. Set "." if magento is installed on project root
    set('magento_dir', '');
    // [Optional] Git repository. Only needed if not using build + artifact strategy
    set('repository', '');
    // Space separated list of languages for static-content:deploy
    set('languages', 'en_US');
    
    set('magento_bin', 'bin/magento');
    
    set('shared_files', ['/var/www/staging/app/etc/env.php']);
    // OPcache configuration
    task('cache:clear:opcache', 'sudo systemctl reload php-fpm');
    after('cache:clear', 'cache:clear:opcache');
    
    // Build host
    localhost('build');
    
    // Remote Servers 
    host('dev_master')
        ->hostname('68.xxx.xxx.124') 
        ->user('root')
        ->set('deploy_path', '/var/www/html')
        ->stage('dev')
        ->roles('master');
    

    I'm using build artifact:

    • php vendor/bin/dep build this goes fine and creates an archived for release

    • php vendor/bin/dep deploy-artifact dev

    It produces the following error:

    [dev_master] > /usr/bin/php /var/www/html/releases/20190305070046/bin/magento setup:db:status
    [dev_master] < No information is available: the Magento application is not installed.
    In Client.php line 99:
      [Deployer\Exception\RuntimeException (1)]
      The command "/usr/bin/php /var/www/html/releases/20190305070046/bin/magento setup:db:status" failed.
      Exit Code: 1 (General error)
      Host Name: dev_master
      ================
      No information is available: the Magento application is not installed.
    

    Can any of you guide me through what am I doing wrong here?

    Reviewed by hamza553 at 2019-03-05 12:04
  • 2. Issue with setup:di:compile

    When magento_dir is set to '.' in my deploy.php, if I run dep build I get the following error:

    The command "cd . && (/usr/bin/php .//bin/magento setup:di:compile)" failed.                                                    
                                                                                                                                      
    Exit Code: 1(General error)                                                                                                     
                                                                                                                                      
    Working directory: /home/user/www/site.uk                                                                               
                                                                                                                                      
    Output:                                                                                                                         
    ================                                                                                                                
    Warning: include(/home/user/www/site.uk/vendor/composer/../../generated/code/Magento/Framework/App/ResourceConnection/  
    Proxy.php): failed to open stream: No such file or directory in /home/user/www/site.uk/vendor/composer/ClassLoader.php on line 444                                                                                                                    
                                                                                                                                      
                                                                                                                                      
    Error Output:                                                                                                                   
    ================  
    

    If I set the magento_dir to an absolute path, it works for the local build but when pushing to production, this path is incorrect and breaks deployment. If I then change it back to '.' it works for production.

    It seems like it should just '.' for local but it throws the ClassLoader.php error. Any ideas?

    Reviewed by stu177 at 2019-01-11 16:03
  • 3. config:remove-dev-modules local instead of remote

    I use git-deployment, so Deployer checks out a branch on the remote server. When using config:remove-dev-modules, this removes the dev-modules on my local machine which causes two problems:

    1. The changed file is never sent to the remote server, so I still get the error bin/magento setup:db:status for which this function was designed.
    2. In theory I could have checked out a branch in which more or less dev-modules are enabled, so just sending the local file to remote can cause problems.

    This is my first time using Deployer, so I don't know what are the possibilities to solve this. I can think of two solutions:

    1. config:remove-dev-modules should run on the server instead of running locally. Maybe this can be done using a replace with sed: sed -i '/<module>/d' ./app/etc/config.php

    2. Download deploy.sh and ./app/etc/config.php from remote, replace locally and send the replaced document back to remote.

    If I can be of any assistance to solve this issue, please let me know.

    Reviewed by luukschakenraad at 2018-10-13 23:48
  • 4. Enable caches in deploy task

    Sometimes a cache type gets disabled, for whatever reason or bug.

    It's nice to make sure the caches you want to be enabled are actually enabled.

    This new task makes sure those caches are enabled. The variable cache_enabled_caches can be changed to add caches from own or 3rd party modules.

    Reviewed by tdgroot at 2019-12-04 10:10
  • 5. Where to install

    Hi,

    As a noob I try to figuring out how to install the deployment tool. Do I have to install this in the Magento root? Or outside the root?

    It would be a little more clear if I know where to cd to. This also applies to the setup part. Where should the file deploy.php copied to?

    I hope you can make it a little more clear for noobs like me ;-)

    Thank you in advanced!

    Reviewed by pdenissen at 2018-04-30 20:26
  • 6. Closes #40. Enhancement: Run Composer optimize autoloader after DI compile.

    I'm merging into master since develop seems behind.

    Disclaimer — I haven't run this in production yet, so give me a few days and I'll can confirm on my end if this works.

    Reviewed by erfanimani at 2020-02-19 11:41
  • 7. Enhancement: Run Composer optimize autoloader after DI compile

    I haven't tested it, but apparently composer dumpautoload -o --apcucan be run after DI compile to speed up PHP class lookups. Might be worth looking into.

    "File system is a bottleneck - make sure composer is optimized and class map is generated after setup di compile. Refer to this tweet of mine:"

    https://twitter.com/IvanChepurnyi/status/1179280000400465920

    Reviewed by erfanimani at 2019-10-30 15:33
  • 8. OpCache Reset

    Since Deployer heavily relies on symlinks and symlinks are cached by the OpCache, a PHP reload or any other OpCache reset command is necessary during the deployment. Currently, this is done via a sudo command:

    https://github.com/jalogut/magento2-deployer-plus/blob/66d1ee4dbc92e10e3ecc250598d12f9d961f110b/deploy.php.sample_2_2_5#L20

    I suggest using the project CacheTool for it, because it does not rely on sudoer rights if I understand correctly.

    What do you think?

    Reviewed by sprankhub at 2019-01-16 13:01
  • 9. Add {{magento_dir}}/pub/static/_cache to shared/writable/clear_paths

    Add path /pub/static/_cache to Shared, Writable and Clear Paths.

    When you have a multi-stage server and merged css or js this folder and subfolders are created to distribute css & js and you need to have it shared.

    Added to clear paths because in each deploy we clean old files that will no longer be used.

    Reviewed by osrecio at 2018-05-18 06:52
  • 10. magento 2.2.3

    Using version ^1.1 for jalogut/magento2-deployer-plus ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages.

    Problem 1 - Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1 - Conclusion: remove symfony/console v2.8.34 - Conclusion: don't install symfony/console v2.8.34 - symfony/yaml v3.4.0 conflicts with symfony/console[v2.8.34]. - symfony/yaml v3.4.1 conflicts with symfony/console[v2.8.34]. - symfony/yaml v3.4.2 conflicts with symfony/console[v2.8.34]. - symfony/yaml v3.4.3 conflicts with symfony/console[v2.8.34]. - symfony/yaml v3.4.4 conflicts with symfony/console[v2.8.34]. - symfony/yaml v3.4.5 conflicts with symfony/console[v2.8.34]. - symfony/yaml v3.4.6 conflicts with symfony/console[v2.8.34]. - symfony/yaml v3.4.7 conflicts with symfony/console[v2.8.34]. - symfony/yaml v3.4.8 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.0 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.1 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.2 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.3 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.4 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.5 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.6 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.7 conflicts with symfony/console[v2.8.34]. - symfony/yaml v4.0.8 conflicts with symfony/console[v2.8.34]. - Conclusion: don't install symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8 - Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1|remove symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8 - Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1|don't install symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8 - Installation request for symfony/console (locked at v2.8.34) -> satisfiable by symfony/console[v2.8.34]. - Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1|remove symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8 - Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1|don't install symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8 - Installation request for jalogut/magento2-deployer-plus ^1.1 -> satisfiable by jalogut/magento2-deployer-plus[1.1, 1.1.1]. - Conclusion: remove symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8 - jalogut/magento2-deployer-plus 1.1 requires deployer/deployer ^6.0 -> satisfiable by deployer/deployer[v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.0.5, v6.1.0]. - deployer/deployer v6.0.0 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8]. - deployer/deployer v6.0.1 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8]. - deployer/deployer v6.0.2 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8]. - deployer/deployer v6.0.3 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8]. - deployer/deployer v6.0.4 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8]. - deployer/deployer v6.0.5 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8]. - deployer/deployer v6.1.0 requires symfony/yaml ~2.7|~3.0|~4.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v4.0.0, v4.0.1, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8]. - symfony/yaml v2.7.0 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.1 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.10 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.11 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.12 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.13 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.14 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.15 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.16 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.17 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.18 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.19 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.2 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.20 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.21 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.22 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.23 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.24 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.25 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.26 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.27 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.28 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.29 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.3 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.30 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.31 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.32 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.33 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.34 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.35 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.36 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.37 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.38 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.39 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.4 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.40 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.41 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.42 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.43 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.44 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.45 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.5 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.6 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.7 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.8 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.7.9 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.0 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.1 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.10 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.11 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.12 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.13 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.14 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.15 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.16 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.17 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.18 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.19 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.2 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.20 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.21 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.22 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.23 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.24 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.25 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.26 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.27 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.28 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.29 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.3 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.30 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.31 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.32 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.33 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.34 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.35 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.36 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.37 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.38 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.4 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.5 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.6 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.7 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.8 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v2.8.9 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.0 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.1 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.2 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.3 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.4 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.5 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.6 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.7 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.8 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.0.9 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.0 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.1 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.10 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.2 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.3 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.4 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.5 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.6 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.7 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.8 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.1.9 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.0 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.1 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.10 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.11 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.12 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.13 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.14 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.2 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.3 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.4 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.5 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.6 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.7 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.8 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.2.9 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.0 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.1 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.10 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.11 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.12 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.13 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.14 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.15 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.16 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.2 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.3 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.4 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.5 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.6 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.7 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.8 conflicts with symfony/dependency-injection[v3.4.4]. - symfony/yaml v3.3.9 conflicts with symfony/dependency-injection[v3.4.4]. - Installation request for symfony/dependency-injection (locked at v3.4.4) -> satisfiable by symfony/dependency-injection[v3.4.4].

    Installation failed, reverting ./composer.json to its original content.

    Reviewed by sivajik34 at 2018-04-10 09:42
  • 11. Magento v2.3.3

    When running

    php vendor/bin/dep -n deploy develop

    PHP Fatal error: Declaration of Symfony\Component\Console\Input\Input::getArgument($name) must be compatible with Symfony\Component\Console\Input\InputInterface::getArgument(string $name) in phar:///opt/atlassian/pipelines/agent/build/vendor/deployer/dist/dep/vendor/symfony/console/Input/Input.php on line 28

    Reviewed by thiagolima-bm at 2020-01-15 15:28
  • 12. Support Composer2 Deployment

    Reviewed by norgeindian at 2021-03-01 21:34
  • 13. Update deployer to newer version

    The old version of deployer throws the following error in the Docker container.

    PHP Fatal error:  require(): Failed opening required 'recipe/common.php' (include_path='phar:///var/www/html/bin/dep/bin/../:.:/usr/share/pear:/usr/share/php') in /var/www/html/vendor/jalogut/magento2-deployer-plus/recipe/magento_2_2_5.php on line 13
    
    Reviewed by tshabatyn at 2020-12-17 20:01
  • 14. artifact exclude rules may exclude vendor files from deploy

    file config/artifact.excludes contains the path "pub/media". This will exclude every path where this pattern is contained. E.g. the amasty module "product-attachment" contains this path vendor/amasty/product-attachment/pub/media/amasty/... which will be excluded too. Solution is to use a leading slash, which is no absolute path but relative to the sync root folder. The other paths are imo not critic.

    Reviewed by jonnsn at 2020-11-06 09:23
  • 15. Cannot run `files:compile`

    When I try to run files:compile, I get the following error:

    The command "cd /srv/public_html/releases/20201105100601 && (/usr/local/bin/php ./bin/magento setup:di:compile)" failed.
    
      Exit Code: 1 (General error)
    
      Host Name: xxxxxxxxxx
    
      ================
    
      In Write.php line 200:
    
        The directory "/srv/public_html/releases/20201105100601/var/cache/" cannot
        be deleted Warning!rmdir(/srv/public_html/releases/20201105100601/var/cache
        /): Not a directory
    
    
      setup:di:compile
    

    The permissions on the symlink are drwxr-xr-x and I'm running as the directory owner.

    We're using absolute symlinks, not sure if that's the issue? Running files:compile works when I do it in the context of a full deploy.

    Reviewed by lfolco at 2020-11-05 15:28
  • 16. Running app:config:import after setup:db-data:upgrade doesn't create new websites/stores

    I found that the current order of commands during a deploy doesn't (fully) import the configuration properly.

    The setup:db-data:upgrade command sets the config_hash in the flag table. This in turns makes the app:config:import think it doesn't need importing. In my case it turns out new website and stores are not created.

    Reversing the order of commands helps out but I'm not sure if that has any side effects.

    Reviewed by rikwillems at 2020-09-21 08:39
Magento2 Deployment with Deployer (Skeleton)

MageDeploy2 Base Magento2 Deployment Setup using Robo and Deployer. This is the base project you should base your deployments on. It provides an confi

Jul 18, 2022
Deployer is a PHP Application deployment system powered by Laravel

Deployer is a PHP Application deployment system powered by Laravel 5.5, written & maintained by Stephen Ball.

Aug 9, 2022
A tool that allows to quickly export data from Magento 1 and Magento 2 store and import it back into Magento 2

Simple Import / Export tool A tool that allows to quickly export data from Magento 1 and Magento 2 store and import it back into Magento 2. Table data

Jun 9, 2022
A block-based child theme for WordPress.org, plus local environment

WordPress.org Block Theme A block-based child theme for WordPress.org, plus local environment. Once set up, this environment will contain some shared

Aug 8, 2022
Migration Tool for Magento Commerce (EE) to Magento OpenSource (CE)

Migration Tool for Magento Commerce to Magento OpenSource Also known as Magento Enterprise (EE) to Magento Community (CE). This migrating tool allows

Aug 3, 2022
A simple, type-safe, zero dependency port of the javascript fetch WebApi for PHP.
A simple, type-safe, zero dependency port of the javascript fetch WebApi for PHP.

A simple, type-safe, zero dependency port of the javascript fetch WebApi for PHP.

Aug 10, 2022
🪃 Zero-dependency global `kirbylog()` helper for any content

Kirbylog The most simple, Kirby-esque way to log content to file. Most of the time, I just want to log some string or array to a file. That's what thi

Jun 17, 2022
📦🚀 Fast, zero config application bundler with PHARs.
📦🚀 Fast, zero config application bundler with PHARs.

Fork of the unmaintained box2 project. This project needs your help! Upgrading from Box2? Checkout the upgrade guide! Goal The Box application simplif

Jul 30, 2022
🧬 Nano is a zero-config, no skeleton, minimal Hyperf distribution that allows you to quickly build a Hyperf application with just a single PHP file.

Nano is a zero-config, no skeleton, minimal Hyperf distribution that allows you to quickly build a Hyperf application with just a single PHP file.

Aug 2, 2022
Run your WP site on github pages, php innovation award winner https://www.phpclasses.org/package/12091-PHP-Make-a-WordPress-site-run-on-GitHub-pages.html
Run your WP site on github pages, php innovation award winner  https://www.phpclasses.org/package/12091-PHP-Make-a-WordPress-site-run-on-GitHub-pages.html

Gitpress Run wordpress directly on github pages Gitpress won the innovation award for may 2021 Read more about this https://naveen17797.github.io/gitp

Apr 8, 2022
A pure PHP implementation of the MessagePack serialization format / msgpack.org[PHP]

msgpack.php A pure PHP implementation of the MessagePack serialization format. Features Fully compliant with the latest MessagePack specification, inc

Jul 26, 2022
Creates Packagist.org mirror site.

Packagist Mirror Creates your own packagist.org mirror site. Requirements PHP ^7.1.3 Installation Clone the repository Install dependencies: php compo

Mar 30, 2020
This Magento extension provides a Real Full Page Caching for Magento powered by Varnish with support of Session-Based information caching (Cart, Customer Accounts, ...) via ESI includes

This Magento extension provides a Real Full Page Caching (FPC) for Magento powered by Varnish with support of Session-Based information caching (Cart, Customer Accounts, ...) via ESI includes

Feb 11, 2022
PHPStorm Live template preferences for Magento 2 Projects
PHPStorm Live template preferences for Magento 2 Projects

Magento 2 PHPStorm Preferences This project is intended to setup useful PHPStorm Templates for Magento 2 Projects. Disclaimer This project overrides t

Jul 18, 2022
PHP_Depend is an adaptation of the established Java development tool JDepend. This tool shows you the quality of your design in terms of extensibility, reusability and maintainability.

PHP Depend Documentation PHP Depend for enterprise Available as part of the Tidelift Subscription. The maintainers of PHP Depend and thousands of othe

Aug 8, 2022
The swiss army knife for Magento developers, sysadmins and devops. The tool provides a huge set of well tested command line commands which save hours of work time. All commands are extendable by a module API.

netz98 magerun CLI tools for Magento 2 The n98 magerun cli tools provides some handy tools to work with Magento from command line. Build Status Latest

Aug 9, 2022
Modularize extensions using symlinks. Voted #1 Magento tool by @WebShopApps!
Modularize extensions using symlinks. Voted #1 Magento tool by @WebShopApps!

modman (Module Manager) Developing extensions for software that doesn't allow you to separate your files from core files, and keeping that extension u

Aug 4, 2022