composer config repositories.amasty composer <path>
<path>
, indicate the repository for a specific Magento edition: https://composer.amasty.com/community
- for community extensions.https://composer.amasty.com/enterprise/
- for enterprise extensions.It is possible to manually save the keys in the repository, so there is no need to get authorized every time. Find the Magento root directory and indicate:
composer config --auth http-basic.composer.amasty.com $COMPOSER_AMASTY_USERNAME $COMPOSER_AMASTY_PASSWORD
Where $COMPOSER_AMASTY_USERNAME
is the Public Key and $COMPOSER_AMASTY_PASSWORD
is the Private Key.
Otherwise, when the customer will be asked for access keys for the first time, they need to agree to save the credentials by printing yes.
composer require amasty/<module-name>
<module-name>
is the Composer name of the extension you are installing. To find the Composer name of the module, open the Products tab of your account and find the Composer packages section:php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy (your locale)
php bin/magento hyva:config:generate -f
cd vendor/hyva-themes/magento2-default-theme/web/tailwind
npm run build-prod
/upload/app
and upload the files to the /app
folder of your Magento website using the ‘Merge’ upload mode. This way, your FTP/SFTP client will only add new files.php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy