Download the PHP package jalogut/magento2-deployer-plus without Composer
On this page you can find all versions of the php package jalogut/magento2-deployer-plus. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package magento2-deployer-plus
Magento 2 Deployer Plus
- 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
Setup
Magento >= 2.1
Magento >= 2.2
Magento >= 2.2.5
Usage
Git deploys:
Build artifact deploys: (only Magento >= 2.2)
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 executesetup:static-content:deploy
individually for each language:
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 executingsetup:static-content:deploy
-
Solution: Skip
setup:static-content:deploy
first time you deploy the new template:-
Temporary disable task
files:static_assets
- Perform a new release
-
Enable back
files:static_assets
on yourdeploy.php
file- Remove
task('files:static_assets')->onRoles('Skip');
- Remove
- Manually execute
files:static_assets
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]