This article describes step-by-step how to migrate from an existing commerce service based integrations to standalone(direct) integrations setup for hospitality.
In this article
Magento extension updates
Customers currently using the Commerce Service–based integrations have the LS Magento extensions installed via Packagist using Composer.
As part of the migration to Standalone (direct) integrations with LS Central, updated code has been introduced in a new GitHub branch (standalone), which is not available on Packagist.
To access these updated integrations, customers must switch their Composer source from Packagist to GitHub (VCS).
Step 1: Register GitHub repositories (VCS)
Add the required GitHub repositories to Composer configuration:
composer config repositories.lsmag-two vcs https://github.com/lsretailomni/lsmag-twocomposer config repositories.hospitality vcs https://github.com/lsretailomni/hospitalityThis ensures Composer fetches the extension source directly from GitHub instead of Packagist.
Step 2: Require the Standalone integration branch
Install the standalone integration code from the new branch:
composer require lsretail/lsmag-two:dev-standalone lsretail/hospitality:dev-standaloneComposer will:
- Switch the package source to GitHub.
- Check out the standalone branch.
- Resolve all dependent modules.
Step 3: Run setup upgrade
Registers configuration changes, and dependency updates.
php bin/magento setup:upgradeMagento configuration changes
Few configuration changes need to be made in the magento admin to resume from Commerce service to standalone (direct) integrations with LS Central. Here is the link to the documentation Configurations-On-Magento.htm
Webhook configuration changes
To make webhooks communication work with the new setup and more securely changes need to be made, in both magento and Central. Here is the link to the documentation Webhooks.htm