diff --git a/.circleci/config.yml b/.circleci/config.yml index cf158778a..f9e3e7e02 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -2,40 +2,37 @@ version: 2.1 jobs: build: machine: - image: ubuntu-2004:202111-01 + image: ubuntu-2004:2022.04.1 steps: - checkout - run: make build check-external-link: machine: - image: ubuntu-2004:202111-01 + image: ubuntu-2004:2022.04.1 steps: - checkout - run: make lint deploy_staging: machine: - image: ubuntu-2004:202111-01 + image: ubuntu-2004:2022.04.1 steps: - checkout - add_ssh_keys - run: name: Deploy on staging server - command: DEPLOY_HOSTNAME=$STAGING_HOSTNAME DEPLOY_PORT=$STAGING_PORT VERSION="6.0" make deploy + command: DEPLOY_HOSTNAME=$STAGING_HOSTNAME DEPLOY_PORT=$STAGING_PORT VERSION="master" make deploy deploy_production: machine: - image: ubuntu-2004:202111-01 + image: ubuntu-2004:2022.04.1 steps: - checkout - add_ssh_keys - run: name: Deploy on production server - command: DEPLOY_HOSTNAME=$PROD_HOSTNAME DEPLOY_PORT=$PROD_PORT VERSION="6.0" make deploy - -orbs: - pull-up: akeneo-orbs/pull-up@1.0 + command: DEPLOY_HOSTNAME=$PROD_HOSTNAME DEPLOY_PORT=$PROD_PORT VERSION="master" make deploy workflows: version: 2 @@ -45,14 +42,14 @@ workflows: filters: branches: ignore: - - '6.0' + - master deployment: jobs: - deploy_staging: filters: branches: - only: '6.0' + only: master - approve_to_deploy_in_production: type: approval requires: @@ -61,20 +58,6 @@ workflows: requires: - approve_to_deploy_in_production - pull_up: - jobs: - - pull-up/pull-up: - from: "6.0" - into: "master" - branch_prefix: "60_to_master" - github_token: MICHEL_TAG_TOKEN - github_username: "micheltag" - slack_webhook: "${SLACK_URL_PULL_UP}" - filters: - branches: - only: - - "6.0" - nightly: triggers: - schedule: @@ -82,6 +65,6 @@ workflows: filters: branches: only: - - "6.0" + - "master" jobs: - check-external-link diff --git a/Dockerfile b/Dockerfile index b58834758..f0cd11249 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,4 +1,4 @@ -FROM akeneo/pim-php-dev:6.0 +FROM akeneo/pim-php-dev:master WORKDIR /home/akeneo/pim-docs/ ENV DEBIAN_FRONTEND=noninteractive diff --git a/cloud_edition/flexibility_mode/docs/system_administration.rst b/cloud_edition/flexibility_mode/docs/system_administration.rst index 3832ba62e..641e61b8d 100644 --- a/cloud_edition/flexibility_mode/docs/system_administration.rst +++ b/cloud_edition/flexibility_mode/docs/system_administration.rst @@ -65,7 +65,6 @@ Alias Argument Action ``partners_systemctl `` ``status|start|stop|restart|enable|disable`` Show status, start/stop/restart or enable/disable job consumers. Refer to `this page `_ for more details ============================ ============================================ ====== - Third-party Software Installation --------------------------------- diff --git a/cloud_edition/flexibility_mode/index.rst b/cloud_edition/flexibility_mode/index.rst index ef726c43f..c0a38d05d 100644 --- a/cloud_edition/flexibility_mode/index.rst +++ b/cloud_edition/flexibility_mode/index.rst @@ -24,24 +24,38 @@ Types of environments The system components are based on :doc:`../../../install_pim/manual/system_requirements/system_requirements`. -Updates and migrations ----------------------- - -Updates can include **patches** and **new features**. Integrators are accountables for applying new patches and performing migrations on the PIM. +PIM updates and migrations +-------------------------- + +Following the `Semantic Version `_, PIM has 2 main updates: + +- patches or minors versions: + Can include **bug fixes** and **new features**. + Integrators are accountable for applying new patches and performing migrations on the PIM. + You can refer to :doc:`../../../migrate_pim/upgrade_minor_version` for more details about the procedure. +- majors versions: + Requires **new versions** of software and various components. + Please contact us through the `Helpdesk > Cloud Flexibility and Serenity `_ to schedule the upgrade of the technological stack. + Then integrators are accountable for performing the PIM migration. + You can refer to :doc:`../../../migrate_pim/upgrade_major_version` for more details about the procedure. + +Quarterly System updates +------------------------ -You can refer to :doc:`../../../migrate_pim/index` for more details about the procedure. +In order for you to benefit the best of Flexibility experience, Akeneo schedules system updates on a quarterly basis. +These updates include **security patches** and **system improvements**. -.. note:: +They will be scheduled every last Wednesday/Thursday of the quarter following these time slots: - Major upgrades can require **new versions** of software and various components. - Please contact us through the `Helpdesk > Cloud Flexibility and Serenity `_ to schedule the upgrade of the tech stack. +- Asia/Australia: Starting **Wednesday at 3pm CET/CEST** +- Europe: Starting **Wednesday at 6pm CET/CEST** +- US: Starting **Thursday at 9am CET/CEST** Backups management ------------------ A snapshot of your production instance is made regularly and can be restored upon request. - Manage your environments ------------------------ .. toctree:: diff --git a/conf.py b/conf.py index c8e47628e..85a98270a 100644 --- a/conf.py +++ b/conf.py @@ -57,7 +57,7 @@ # built documents. # # The short X.Y version. -version = os.getenv('PIM_VERSION', '6.0') +version = os.getenv('PIM_VERSION', 'master') # Warning: These versions will be deleted on documentation deploy. versions = os.getenv('PIM_VERSIONS', 'master') diff --git a/contribute_to_pim/create_connector.rst b/contribute_to_pim/create_connector.rst index 83401a08e..c82bf78ce 100644 --- a/contribute_to_pim/create_connector.rst +++ b/contribute_to_pim/create_connector.rst @@ -3,8 +3,8 @@ How to contribute to a Connector? We're happy to connect the PIM to any third-party system! -* Begin by checking on the `Akeneo PIM Marketplace`_ that nobody published a connector for a 3rd party system +* Begin by checking on the `Akeneo App Store`_ that nobody published a connector for a 3rd party system * Create your connector :doc:`/import_and_export_data/guides/create-connector` -* Reference it on the `Akeneo PIM Marketplace`_ +* Reference it on the `Akeneo App Store`_ -.. _Akeneo PIM Marketplace: https://marketplace.akeneo.com/ +.. _Akeneo App Store: https://marketplace.akeneo.com/ diff --git a/contribute_to_pim/tests/establishing_decorator_pattern.rst b/contribute_to_pim/tests/establishing_decorator_pattern.rst index 798197197..088b3e723 100644 --- a/contribute_to_pim/tests/establishing_decorator_pattern.rst +++ b/contribute_to_pim/tests/establishing_decorator_pattern.rst @@ -86,7 +86,7 @@ Navigate And Change The Current Page } Selenium will know which URL to go to thanks to `the protected $path attribute -`_ +`_ contained in *Context\\Page\\Role\\Edit*. You may notice that this Gherkin method still uses the old implementation of Behat in Akeneo PIM. @@ -102,7 +102,7 @@ This organization is very helpful to quickly find the context you are looking fo We are working on permissions that are localized in the system main menu. So let's see the `\\Pim\\Behat\\Context\\Domain\\System\\PermissionsContext -`_. +`_. .. image:: images/PermissionsContext.png @@ -149,12 +149,12 @@ Pages _____ The current page is `Context\\Page\\Role\\Edit -`_. +`_. When you call *Pim\\Behat\\Context\\NavigationContext->getCurrentPage()* the method will match "Role edit" to *return new Context\\Page\\Role\\Edit()*. That's why all of our pages are located in a folder named after the name of the Entity. In this folder, each action has its dedicated page such as Index.php, Creation.php, Edit.php as you can see -in the `Role folder `_ for example. +in the `Role folder `_ for example. .. image:: images/edit.png @@ -247,7 +247,7 @@ The name of the sub-folder is only the representative name of the element, no pr have to be suffixed by "Decorator" like *DecoratedElementDecorator*. The `Pim\\Behat\\Decorator\\Permission\\PermissionDecorator -`_ +`_ adds behaviors to an Element to be able to navigate between groups and grant or revoke permissions for resources or groups. .. image:: images/decorator.png @@ -303,7 +303,7 @@ The method *$this->find()* is neither in the decorator nor in the abstract class That's how we can call methods from the Element class inside decorators. And obviously, that's why all decorators must extend `Pim\\Behat\\Decorator\\ElementDecorator -`_. +`_. .. note:: diff --git a/contribute_to_pim/tests/index.rst b/contribute_to_pim/tests/index.rst index 25c82fa98..619dc1095 100644 --- a/contribute_to_pim/tests/index.rst +++ b/contribute_to_pim/tests/index.rst @@ -2,7 +2,7 @@ How behavior tests are architectured in the PIM? ================================================ -The PIM comes with a set of Behat scenarios: https://github.com/akeneo/pim-community-dev/tree/6.0/tests/legacy/features +The PIM comes with a set of Behat scenarios: https://github.com/akeneo/pim-community-dev/tree/master/tests/legacy/features .. warning:: diff --git a/contribute_to_pim/translate.rst b/contribute_to_pim/translate.rst index ff057550c..81f4830f2 100644 --- a/contribute_to_pim/translate.rst +++ b/contribute_to_pim/translate.rst @@ -36,13 +36,13 @@ Then, copy the translations in the right folders: .. code-block:: bash - cp -r crowdin_archive/6.0/Community/* your_app/vendor/akeneo/pim-community-dev/ + cp -r crowdin_archive/master/Community/* your_app/vendor/akeneo/pim-community-dev/ If you use the Enterprise Edition, run this command too: .. code-block:: bash - cp -r crowdin_archive/6.0/Enterprise/* your_app/vendor/akeneo/pim-enterprise-dev/ + cp -r crowdin_archive/master/Enterprise/* your_app/vendor/akeneo/pim-enterprise-dev/ Then, update the parameters of `your_app/vendor/akeneo/pim-community-dev/src/Akeneo/Platform/Bundle/UIBundle/Resources/config/locale_provider.yml` to change the minimum percentage and add your new language (here, 10% and Hungarian): diff --git a/import_and_export_data/simple-import.rst b/import_and_export_data/simple-import.rst index 3725a29da..27a6cc118 100644 --- a/import_and_export_data/simple-import.rst +++ b/import_and_export_data/simple-import.rst @@ -1,8 +1,8 @@ How import works ================ -.. _minimal: https://github.com/akeneo/pim-community-dev/tree/6.0/src/Akeneo/Platform/Bundle/InstallerBundle/Resources/fixtures/minimal -.. _icecat: https://github.com/akeneo/pim-community-dev/tree/6.0/src/Akeneo/Platform/Bundle/InstallerBundle/Resources/fixtures/icecat_demo_dev +.. _minimal: https://github.com/akeneo/pim-community-dev/tree/master/src/Akeneo/Platform/Bundle/InstallerBundle/Resources/fixtures/minimal +.. _icecat: https://github.com/akeneo/pim-community-dev/tree/master/src/Akeneo/Platform/Bundle/InstallerBundle/Resources/fixtures/icecat_demo_dev At any time, a set of data can be imported: products, attributes, users, etc. diff --git a/manipulate_pim_data/mass_edition/register_a_new_mass_edit_action.rst b/manipulate_pim_data/mass_edition/register_a_new_mass_edit_action.rst index b785241bf..288b87ca8 100644 --- a/manipulate_pim_data/mass_edition/register_a_new_mass_edit_action.rst +++ b/manipulate_pim_data/mass_edition/register_a_new_mass_edit_action.rst @@ -8,7 +8,7 @@ on selected products. Prerequisite ------------ The mass edit action uses the `BatchBundle -`_ in order to run mass edit in the background. Readers and Writers are already +`_ in order to run mass edit in the background. Readers and Writers are already created so in this cookbook we will focus on how to create a Mass Edit Action and create a Processor. For more information on how to create Jobs, Readers, Processors, or Writers please see :doc:`/import_and_export_data/index`. diff --git a/manipulate_pim_data/non-product/create.rst b/manipulate_pim_data/non-product/create.rst index 07a83d53d..69c9b6f2d 100644 --- a/manipulate_pim_data/non-product/create.rst +++ b/manipulate_pim_data/non-product/create.rst @@ -1,7 +1,7 @@ How to Create Non-Product Objects ================================= -.. _SimpleFactoryInterface: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Tool/Component/StorageUtils/Factory/SimpleFactoryInterface.php +.. _SimpleFactoryInterface: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Tool/Component/StorageUtils/Factory/SimpleFactoryInterface.php To create common objects, we rely on different methods depending on the complexity of the object. There are some examples on how to use these services. diff --git a/migrate_pim/upgrade/upgrade_from_40_to_50.rst b/migrate_pim/upgrade/upgrade_from_40_to_50.rst index 07e7b1c9b..9cb956a1c 100644 --- a/migrate_pim/upgrade/upgrade_from_40_to_50.rst +++ b/migrate_pim/upgrade/upgrade_from_40_to_50.rst @@ -234,3 +234,9 @@ From that point, you will have to migrate your bundle one by one. Remember to check if they are still relevant, as each Akeneo version brings new features. + + +Setting up the Events API +************************* + +Configure your Events API with :doc:`/install_pim/manual/events_api` diff --git a/migrate_pim/upgrade/upgrade_from_50_to_60.rst b/migrate_pim/upgrade/upgrade_from_50_to_60.rst index e21ba3472..9ad9bcbf9 100644 --- a/migrate_pim/upgrade/upgrade_from_50_to_60.rst +++ b/migrate_pim/upgrade/upgrade_from_50_to_60.rst @@ -7,7 +7,7 @@ Disclaimer ********** Make sure your production database is backed-up before performing the data migration. -The queue daemon(s) must be stopped as well. +The queue daemon(s) must be stopped as well (:doc:`/cloud_edition/flexibility_mode/docs/job_consumers_and_workers`). Prepare your project for the new technical stack ************************************************ diff --git a/migrate_pim/upgrade/upgrade_from_60_to_70.rst b/migrate_pim/upgrade/upgrade_from_60_to_70.rst new file mode 100644 index 000000000..2c24a89e1 --- /dev/null +++ b/migrate_pim/upgrade/upgrade_from_60_to_70.rst @@ -0,0 +1,213 @@ +Upgrade from 6.0 to 7.0 +~~~~~~~~~~~~~~~~~~~~~~~ + +Use this documentation to upgrade projects based on Akeneo PIM Community Edition or Enterprise Edition 6.0 to 7.0. + +Disclaimer +********** + +Make sure your production database is backed-up before performing the data migration. +The queue daemon(s) must be stopped as well. + +Prepare your project for the new technical stack +************************************************ + +Your current v6.0 application must have up to date migrations before migrating on the new technical stack. + +The root of your current installation dir is referred as $INSTALLATION_DIR. + +.. code:: bash + + $ export APP_ENV=prod + $ cd $INSTALLATION_DIR + $ cp -R ./vendor/akeneo/pim-community-dev/upgrades/* ./upgrades/ + $ cp -R ./vendor/akeneo/pim-enterprise-dev/upgrades/* ./upgrades/ + $ php bin/console doctrine:migrations:version --add --all -q + $ rm -rf var/cache/ + +.. note:: + + WARNING: please note that this part of the migration needs to be executed on your PIM v6.0 ``before`` upgrading your technical stack. + + +Requirements +************ + +Updated System components +------------------------- + +You have to make sure your system components are updated to the version required for Akeneo PIM: + - PHP 8.0 + - MySQL 8.0 + - Elasticsearch 7.16 + + +Updated System dependencies +--------------------------- +Check your system dependencies are in sync with :doc:`/install_pim/manual/system_requirements/system_requirements` + + +Updated crontab definition +-------------------------- + +Check your crontab is in sync with :doc:`/cloud_edition/flexibility_mode/docs/crontasks` + + +Prepare your project +******************** + +Akeneo PIM composer.json +---------------------------- +The root of your current installation dir is referred as $INSTALLATION_DIR. + +Community Edition +^^^^^^^^^^^^^^^^^ + +You can download the composer.json file directly from the Github repository: + +.. code:: bash + + $ curl https://raw.githubusercontent.com/akeneo/pim-community-standard/7.0/composer.json > $INSTALLATION_DIR/composer.json + +Enterprise Edition +^^^^^^^^^^^^^^^^^^ +Please visit your `Akeneo Portal `_ to download the archive. + +.. code:: bash + + $ tar xvzf pim-enterprise-standard-.tar.gz -C $INSTALLATION_DIR --strip-components 1 pim-enterprise-standard/composer.json + +Load your PIM Enterprise dependencies +***************************************** + +.. code:: bash + + $ composer update + +.. note:: + + You may need to increase the memory provided to `composer`, as this step can be very memory consuming: + + .. code:: bash + + $ php -d memory_limit=4G /path/to/composer update + +Let Akeneo PIM continue the preparation for you +*************************************************** + +Community Edition +----------------- + +.. code:: bash + + $ export APP_ENV=prod + $ vendor/akeneo/pim-community-dev/std-build/migration/prepare_60_to_70.sh + + +Enterprise Edition +------------------ + +.. code:: bash + + $ export APP_ENV=prod + $ vendor/akeneo/pim-enterprise-dev/std-build/upgrade/prepare_60_to_70.sh + +.. warning:: + This script overwrites several configuration files. + + In case of customisation, you need to resolve conflicts. + +Make sure your environment is ready to be migrated +************************************************** + +.. code:: bash + + $ rm -Rf var/cache + $ bin/console pim:installer:check-requirements + +If this command detects something not working or not properly configured, +please fix the problem before continuing. + +Prepare the front +***************** + +.. code:: bash + + $ make upgrade-front + +Migrate your data +***************** + +.. code:: bash + + $ bin/console pim:data-quality-insights:clean-product-scores + $ bin/console doctrine:migrations:migrate + $ bin/console pim:data-quality-insights:populate-product-models-scores-and-ki + +.. note:: + + You may receive the following warnings: + + WARNING! You have X previously executed migrations in the database that are not registered migrations. + + + This can be safely ignored as this only means that your database is up to date, but without finding the corresponding + migration files. + + Another message could be `Migration _X_Y_ZZZZ was executed but did not result in any SQL statements`. + + This makes sense for some migration that only touches the Elasticsearch index or don't apply because no data linked + to this migration have been found. + + The message "The migration has already been performed." concerning the "data-quality-insights" migration could be ignored . + + +Migrating your custom code +************************** + +Applying automatic fixes +------------------------ + +Some changes we made in the code of Akeneo PIM can be automatically applied to your own code. + +In order to make this process easier and more error proof, we decided to use PHP Rector (https://github.com/rectorphp/rector) +to apply these changes. + + +Installing Rector +^^^^^^^^^^^^^^^^^ + +.. code:: bash + + composer require --dev rector/rector-prefixed + +Applying automatic fixes +^^^^^^^^^^^^^^^^^^^^^^^^ + +.. code:: bash + + vendor/bin/rector process src/ + + +.. note:: + + This will use the `rector.yaml` file created by the `prepare.sh` above. + Feel free to add your own refactoring rules inside it. More information on https://getrector.org/ + +Identifying broken code +^^^^^^^^^^^^^^^^^^^^^^^^ + +You can use PHPStan to help you identify broken code: + + +.. code:: bash + + composer require --dev phpstan/phpstan + vendor/bin/phpstan analyse src/ + +More information, please check https://github.com/phpstan/phpstan + +From that point, you will have to migrate your bundle one by one. + +Remember to check if they are still relevant, as each Akeneo version +brings new features. diff --git a/migrate_pim/upgrade_major_version.rst b/migrate_pim/upgrade_major_version.rst index e29c8ab9c..52bfc1b80 100644 --- a/migrate_pim/upgrade_major_version.rst +++ b/migrate_pim/upgrade_major_version.rst @@ -69,3 +69,13 @@ Use this documentation to migrate projects based on Akeneo PIM Community Edition :maxdepth: 1 upgrade/upgrade_from_50_to_60 + +Upgrade from 6.0 to 7.0 +----------------------- + +Use this documentation to migrate projects based on Akeneo PIM Community Edition or Enterprise Edition 6.0 to 7.0. + +.. toctree:: + :maxdepth: 1 + + upgrade/upgrade_from_60_to_70 diff --git a/technical_architecture/best_practices/core/standards.rst b/technical_architecture/best_practices/core/standards.rst index c50ae4d19..ef599713b 100644 --- a/technical_architecture/best_practices/core/standards.rst +++ b/technical_architecture/best_practices/core/standards.rst @@ -5,7 +5,7 @@ When contributing code to Akeneo PIM, you must follow its coding standards (very Akeneo follows the standards defined in the `PSR-0`_, `PSR-1`_ and `PSR-2`_ documents. -We use few extra rules defined in our configuration of php-cs-fixer https://github.com/akeneo/pim-community-dev/blob/6.0/.php_cs.php. +We use few extra rules defined in our configuration of php-cs-fixer https://github.com/akeneo/pim-community-dev/blob/master/.php_cs.php. Example ------- diff --git a/technical_architecture/best_practices/reusable_bundle.rst b/technical_architecture/best_practices/reusable_bundle.rst index d8d2db6f9..ee67a5749 100644 --- a/technical_architecture/best_practices/reusable_bundle.rst +++ b/technical_architecture/best_practices/reusable_bundle.rst @@ -131,7 +131,7 @@ For your own model classes, create your class and its interface. Then you can rely on your interface and use the `Akeneo target resolver`_ which is based on the `Doctrine target entity resolver`_. .. _oneToOne unidirectional association: https://www.doctrine-project.org/projects/doctrine-orm/en/2.5/reference/association-mapping.html#one-to-one-unidirectional -.. _Akeneo target resolver: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Tool/Bundle/StorageUtilsBundle/DependencyInjection/Compiler/AbstractResolveDoctrineTargetModelPass.php +.. _Akeneo target resolver: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Tool/Bundle/StorageUtilsBundle/DependencyInjection/Compiler/AbstractResolveDoctrineTargetModelPass.php .. _Doctrine target entity resolver: https://symfony.com/doc/4.4/doctrine/resolve_target_entity.html diff --git a/technical_architecture/events/storage_events.rst b/technical_architecture/events/storage_events.rst index 4faa8dac9..9d48587e4 100644 --- a/technical_architecture/events/storage_events.rst +++ b/technical_architecture/events/storage_events.rst @@ -2,7 +2,7 @@ Storage events ============== .. _GenericEvent: https://github.com/symfony/symfony/blob/4.4/src/Symfony/Component/EventDispatcher/GenericEvent.php -.. _RemoveEvent: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Tool/Component/StorageUtils/Event/RemoveEvent.php +.. _RemoveEvent: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Tool/Component/StorageUtils/Event/RemoveEvent.php Storage events are dispatched in the PIM when you manipulate data using the savers and removers services. They are basically useful if you want to add your business logic before or after an object is saved or removed. @@ -33,8 +33,8 @@ ProjectSubscriber (Enterprise edition) 0 CheckPublishedProductOnRemovalSubscriber (Enterprise edition) 0 ================================================================ =============== -.. _CheckChannelsOnDeletionSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/Category/OnDelete/CheckChannelsOnDeletionSubscriber.php -.. _AddRemoveVersionSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Tool/Bundle/VersioningBundle/EventSubscriber/AddRemoveVersionSubscriber.php +.. _CheckChannelsOnDeletionSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/Category/OnDelete/CheckChannelsOnDeletionSubscriber.php +.. _AddRemoveVersionSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Tool/Bundle/VersioningBundle/EventSubscriber/AddRemoveVersionSubscriber.php ``akeneo.storage.post_remove`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -52,8 +52,8 @@ Listener Class Name Priority `ProductModel\\OnDelete\\ComputeProductAndAncestorsSubscriber`_ 0 =============================================================== =============== -.. _Product\\OnDelete\\ComputeProductsAndAncestorsSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/Product/OnDelete/ComputeProductsAndAncestorsSubscriber.php -.. _ProductModel\\OnDelete\\ComputeProductAndAncestorsSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/ProductModel/OnDelete/ComputeProductAndAncestorsSubscriber.php +.. _Product\\OnDelete\\ComputeProductsAndAncestorsSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/Product/OnDelete/ComputeProductsAndAncestorsSubscriber.php +.. _ProductModel\\OnDelete\\ComputeProductAndAncestorsSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/ProductModel/OnDelete/ComputeProductAndAncestorsSubscriber.php ``akeneo.storage.pre_remove_all`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -89,9 +89,9 @@ ProjectSubscriber (Enterprise edition) 0 EnsureProductDraftGlobalStatusSubscriber (Enterprise edition) 0 ============================================================= =============== -.. _CurrencyDisablingSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Channel/Bundle/EventListener/CurrencyDisablingSubscriber.php -.. _ComputeEntityRawValuesSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/EntityWithValues/ComputeEntityRawValuesSubscriber.php -.. _ChannelLocaleSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Channel/Bundle/EventListener/ChannelLocaleSubscriber.php +.. _CurrencyDisablingSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Channel/back/Infrastructure/EventListener/CurrencyDisablingSubscriber.php +.. _ComputeEntityRawValuesSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/EntityWithValues/ComputeEntityRawValuesSubscriber.php +.. _ChannelLocaleSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Channel/back/Infrastructure/EventListener/ChannelLocaleSubscriber.php ``akeneo.storage.post_save`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -111,8 +111,8 @@ CatalogUpdatesSubscriber (Enterprise edition) 0 ImportProposalsSubscriber (Enterprise edition) 0 =============================================================== =============== -.. _Product\\OnSave\\ComputeProductsAndAncestorsSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/Product/OnSave/ComputeProductsAndAncestorsSubscriber.php -.. _ProductModel\\OnSave\\ComputeProductAndAncestorsSubscriber: https://github.com/akeneo/pim-community-dev/blob/6.0/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/ProductModel/OnSave/ComputeProductAndAncestorsSubscriber.php +.. _Product\\OnSave\\ComputeProductsAndAncestorsSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/Product/OnSave/ComputeProductsAndAncestorsSubscriber.php +.. _ProductModel\\OnSave\\ComputeProductAndAncestorsSubscriber: https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Pim/Enrichment/Bundle/EventSubscriber/ProductModel/OnSave/ComputeProductAndAncestorsSubscriber.php ``akeneo.storage.pre_save_all`` diff --git a/technical_architecture/technical_information/recommended_configuration.rst b/technical_architecture/technical_information/recommended_configuration.rst index 102693f90..890d53839 100644 --- a/technical_architecture/technical_information/recommended_configuration.rst +++ b/technical_architecture/technical_information/recommended_configuration.rst @@ -12,17 +12,17 @@ Software -------- +-------------------+------------------------------------------------------------------------------------------------------------+ -| Debian (Linux) | 9 (64 bits) | +| Debian (Linux) | 10 (64 bits) | +-------------------+------------------------------------------------------------------------------------------------------------+ -| or Ubuntu | 16.04 (64 bits) | +| or Ubuntu | 18.04 (64 bits) | +-------------------+------------------------------------------------------------------------------------------------------------+ | Apache Web Server | ≥ 2.4 | +-------------------+------------------------------------------------------------------------------------------------------------+ -| PHP (FPM not CGI) | 7.2 | +| PHP (FPM not CGI) | 8.0 | +-------------------+------------------------------------------------------------------------------------------------------------+ -| MySQL | 5.7 | +| MySQL | 8.0 | +-------------------+------------------------------------------------------------------------------------------------------------+ -| Elasticsearch | 5.5 ≤ version < 6 | +| Elasticsearch | 7.4 ≤ version | +-------------------+------------------------------------------------------------------------------------------------------------+ .. warning:: diff --git a/use_sso_authentication/index.rst b/use_sso_authentication/index.rst index ca43551b2..0cb33c207 100644 --- a/use_sso_authentication/index.rst +++ b/use_sso_authentication/index.rst @@ -100,7 +100,7 @@ This container will expose the ``8082`` port, you can override this value in the You can access the IdP administration page at the following url: http://localhost:8082/simplesaml. -| Some users are already configured, the same that are in the `icecat_demo_dev fixtures `_. +| Some users are already configured, the same that are in the `icecat_demo_dev fixtures `_. | They are defined in the ``docker/sso_authsources.php``.