QuestionQ35

VerifiedSetup/configuring Adobe Commerce Cloud

An Adobe Commerce developer creates a new website by using a data patch. Each website will have unique pricing by website. The developer does not have access to the production and staging environments, so they do not know the current configuration.

How can they ensure the configuration is deployed and consistent across all environments?

Explanation

bin/magento config:set catalog/price/scope 1 --lock-config writes the setting to the shared app/etc/config.php file, which can be committed and deployed consistently across environments. The setting is also locked against Admin changes. A plain config:set changes only the current environment’s database configuration, while a module config.xml value is merely a default that higher-precedence configuration can override.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!