Skip to content

Commit

Permalink
Merge pull request #1 from zepgram/develop
Browse files Browse the repository at this point in the history
[release 0.0.2] fix composer dependencies
  • Loading branch information
Benjamin Calef authored May 20, 2020
2 parents c2f4226 + 29af654 commit b6709e5
Show file tree
Hide file tree
Showing 5 changed files with 8 additions and 7 deletions.
4 changes: 2 additions & 2 deletions Model/Plugin/ChangeDetector.php → Model/ChangeDetector.php
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
<?php
/**
* This file is part of Zepgram\ZeroDowntimeDeployment\Model\Plugin
* This file is part of Zepgram\ZeroDowntimeDeployment\Model
*
* @package Zepgram\ZeroDowntimeDeployment
* @file ChangeDetector.php
Expand All @@ -13,7 +13,7 @@

declare(strict_types=1);

namespace Zepgram\ZeroDowntimeDeployment\Model\Plugin;
namespace Zepgram\ZeroDowntimeDeployment\Model;

use Magento\Deploy\Model\DeploymentConfig\ChangeDetector as MagentoChangeDetector;
use Magento\Deploy\Model\DeploymentConfig\DataCollector;
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,9 @@ For example:

The mainly steps to reach the ZDD with Magento2:
1. Start the deployment: green pods are the old one, for now they must stay active while creating blue pods.
1. You must set your blue pods to a dedicated redis database and keep the green pods on their own redis db (avoiding cache corrupting).
1. Run `bin/magento setup:upgrade --keep-generated` to upgrade your database.
1. Upgrading is done: now green pods must be killed and replaced by blue pods based on health check statement.
1. Even if cache has been already cleared by `bin/magento setup:upgrade` you must clean it again with `bin/magento cache:flush` because old pods may corrupt your cache.

You can find a lot of articles detailling the procedure:
- https://inviqa.com/blog/how-achieve-zero-downtime-deployments-magento-2
Expand Down
5 changes: 3 additions & 2 deletions composer.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,10 @@
"name": "zepgram/module-zero-downtime-deployment",
"description": "Disable native change detection when Magento2 is on production mode to allow Zero Downtime Deployment (ZDD)",
"type": "magento2-module",
"version": "0.0.1",
"version": "0.0.2",
"require": {
"magento/framework": "^101.0.7|^102.0.0"
"magento/framework": "^102.0.0",
"magento/module-deploy": "^100.2.0"
},
"autoload": {
"files": [
Expand Down
2 changes: 1 addition & 1 deletion etc/di.xml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
<type name="Magento\Deploy\Model\Plugin\ConfigChangeDetector">
<arguments>
<argument name="changeDetector" xsi:type="object">
Zepgram\ZeroDowntimeDeployment\Model\Plugin\ChangeDetector
Zepgram\ZeroDowntimeDeployment\Model\ChangeDetector
</argument>
</arguments>
</type>
Expand Down
2 changes: 1 addition & 1 deletion etc/module.xml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
-->
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:framework:Module/etc/module.xsd">
<module name="Zepgram_ZeroDowntimeDeployment" setup_version="0.0.1">
<module name="Zepgram_ZeroDowntimeDeployment" setup_version="0.0.2">
<sequence>
<module name="Magento_Deploy"/>
</sequence>
Expand Down

0 comments on commit b6709e5

Please sign in to comment.