repository·develop·Indexed 21 days ago
https://github.com/netz98/n98-magerun2A powerful CLI toolset for managing Magento 2, Mage-OS, and Adobe Commerce environments. It provides a comprehensive suite of commands for database operations, cache management, configuration, and developer workflows, including specialized admin user management and token creation.
n98-magerun2 provides a suite of commands to manage Magento's Entity-Attribute-Value (EAV) model. EAV is the flexible data model used for entities like products and customers. You can use these commands to list available attributes, inspect the data associated with a specific attribute, or remove attributes by their code.
Available EAV commands:
eav:attribute:list: Lists EAV attributes.eav:attribute:view: Views the data for a specific attribute.eav:attribute:remove: Removes an attribute based on its attribute code.n98-magerun2 is a command-line tool designed to automate and simplify tasks for Adobe Commerce, Magento, and Mage-OS environments. It serves different user roles through specific capabilities:
You can extend the core functionality of n98-magerun2 by installing third-party modules. These modules add specialized commands for security, performance, maintenance, and API discovery.
Modules are categorized by their primary use case:
giftcard command group in n98-magerun2 provides tools for automating and managing gift card workflows within a Magento store. You can use these commands to generate pools, create individual cards, inspect card details, and remove existing cards.bin/magento commands through the magerun2 CLI. This is useful for environments where you want to use the enhanced features of magerun2 while still interacting with the core Magento command set. These commands are typically prefixed or mapped to ensure they are routed correctly through the magerun2 execution engine.n98-magerun2 uses a hierarchical configuration system that allows you to extend or overwrite built-in settings. Configurations are loaded from multiple levels and merged into a single configuration set.
When multiple configuration files define the same key, the value from the higher-precedence level wins. The merging order (from lowest to highest precedence) is:
script command that allows you to automate repetitive tasks by running a sequence of multiple n98-magerun2 commands defined in a script file. Instead of executing commands manually one by one, you can consolidate them into a single file and execute them via the script command.n98-magerun2 merges configuration from multiple sources to allow for flexible overrides. Each subsequent level in the hierarchy can override values defined in the previous levels. The final configuration used by the tool is the result of this cumulative merge process.
The merge order is:
Values defined in the Project level config have the highest priority and will override values from all other levels.
Magento initialization is a multi-step process managed by the N98\Magento\Application class to ensure the CLI tool operates within a valid Magento context. The process follows these stages:
Application class (extending Symfony's Console Application) manages configuration, event dispatching, and initialization state.MagentoDetector class locates the installation by checking the current working directory, command-line options (e.g., --root-dir), or specific environment variables.Magento1Initializer or Magento2Initializer is used to bootstrap the correct version, setting up autoloaders and the Magento application context.MagentoHelper and event listeners are initialized to provide integration points for commands.Any package you add to the composer:redeploy-base-packages list must contain a static file mapping in its composer.json file to be correctly redeployed. This mapping is defined within the extra.map key.
"extra": {
"map": [
[
".editorconfig",
".editorconfig"
]
]
}Since n98-magerun2 is built on the Symfony Console component, you can hook into the CLI command lifecycle by listening to Symfony's built-in events. This allows you to modify input/output, perform cleanup, or handle errors without changing the command code itself.
Key Symfony events available:
ConsoleEvents::COMMAND: Dispatched before a command is executed. Use this to modify input/output or prevent execution.ConsoleEvents::TERMINATE: Dispatched after a command finishes. Use this for logging or cleanup.ConsoleEvents::ERROR: Dispatched if an exception occurs. Use this to handle or log errors.```php
use Symfony\Component\EventDispatcher\EventSubscriberInterface;
use Symfony\\