Download the PHP package n98/magerun2 without Composer

netz98 magerun CLI tools for Magento 2

The n98 magerun CLI Tools provides some handy tools to work with Magento / Mage-OS / Adobe Commerce from command line.

The swiss army knife for Magento developers, sysadmins and devops

Build Status

Latest Release
Development Branch

Development is done in develop branch.

This software is only running with Magento 2.

If you use Magento 1 please use another stable version (https://github.com/netz98/n98-magerun).

Compatibility

The tools will automatically be tested for multiple PHP versions. It's currently running in various Linux distributions and Mac OS X. Microsoft Windows is not fully supported (some Commands like db:dump or install are excluded).

We support the following Magento Versions:

• 2.4.x Open Source/Commerce
• 2.3.x Open Source/Commerce (last compatible n98-magerun2 version is v5.2.0)
• 2.2.x Open Source/Commerce (last compatible n98-magerun2 version is v3.2.0)

We support the following PHP Versions:

• PHP 8.3
• PHP 8.2
• PHP 8.1
• PHP 7.4
• PHP 7.3 (last compatible version is v6.1.1)
• PHP 7.2 (last compatible version is v4.7.0)

Installation

There are three ways to install the tools:

Download and Install Phar File

Download the latest stable n98-magerun phar-file from the file-server:

or if you prefer to use Curl:

Verify the download by comparing the SHA256 checksum with the one on the website:

It is also possible to verify automatically:

If it shows the same checksum as on the website, you downloaded the file successfully.

Now you can make the phar-file executable:

The base-installation is now complete and you can verify it:

The command should execute successfully and show you the version number of N98-Magerun like:

n98-magerun2 version 4.8.0 by valantic CEC

You now have successfully installed Magerun! You can tailor the installation further like installing it system-wide and enable autocomplete - read on for more information about these and other features.

If you want to use the command system wide you can copy it to /usr/local/bin.

Install the phar via Composer

We offer a special dist package to install the phar file via Composer. See https://packagist.org/packages/n98/magerun2-dist for more details. The main advantage of the dist package is that there are no package dependencies.

Install with Composer (Source Package) - not recommended

The installation via Composer is not recommended, because it's impossible to be compatible with all project and Magento core dependencies. Please use the phar file instead of the Composer version. We are not able to provide compatibility to all Magento versions anymore.

Update

There is a self-update command available. This works only for phar-distribution.

With --dry-run option it is possible to download and test the phar file without replacing the old one.

Autocompletion

Files for autocompletion with Magerun can be found inside the folder res/autocompletion, In the following some more information about a specific one (Bash), there are more (e.g. Fish, Zsh).

Bash

Bash completion is available pre-generated, all commands and their respective options are availble on tab. To get completion for an option type two dashes (--) and then tab.

To install the completion files, copy n98-magerun2.phar.bash to your bash compatdir folder for autocompletion.

On my Ubuntu system this can be done with the following command:

The concrete folder can be obtained via pkg-config:

Detailed information is available in the bash-completions FAQ: https://github.com/scop/bash-completion#faq

Usage / Commands

NOTE There are more commands available as documented here. Please use the list command to see all.

All commands try to detect the current Magento root directory. If you have multiple Magento installations you must change your working directory to the preferred installation.

You can list all available commands by:

If you don't have the .phar file installed system wide you can call it with the PHP CLI interpreter:

Global config parameters:

Call Core Magento Commands

The tool can be used to run core Magento commands. We provide a internal Proxy Command which calls the original Magento command via bin/magento. All options and arguments are passed to the original command.

If you do not want to use the proxy command you can disable it with the --skip-core-commands option.

One of the big advantages of the proxy command is that you can run any command without having to change the working directory to the Magento root directory or to specify the path to bin/magento if your current working directory is inside the Magento installation.

If you are outside the Magento root directory you can run any command by specifying the Magento root directory with the --root-dir option. That is very useful if you have multiple Magento installations or if it is used in some kind of automation.

For core commands we filter environment variables to avoid problems with enabled xdebug extension.

Open Shop in Browser

Customer Info

Loads basic customer info by email address.

Create customer

Creates a new customer/user for shop frontend.

Example:

You can add additional any number of custom fields, example:

List Customers

List customers. The output is limited to 1000 (can be changed by overriding config). If search parameter is given the customers are filtered (searchs in firstname, lastname and email).

Change customer password

• Website parameter must only be given if more than one websites are available.

Create Customer Token for Webapi

Delete customer

Examples:

Deletes customer(s) by given id or a combination of the website id and email or website id and firstname and lastname. In addition, you can delete a range of customer ids or delete all customers.

Add customer address

Examples:

Adds a customer address to given customer defined by email and website

Magento Installer

• Downloads Composer (if not already installed)
• Downloads Magento 2.
• Tries to create database if it does not exist.
• Installs Magento sample data.
• Starts Magento installer
• Sets rewrite base in .htaccess file

Interactive installer:

Unattended installation:

Example of an unattended Magento CE 2.0.0.0 dev beta 1 installation:

Additionally, with --noDownload option you can install Magento working copy already stored in --installationFolder on the given database.

Magento System Info

Provides infos like the edition, version or the configured cache backends, amount of data or installed packages.

Options:

Magento Stores

Lists all store views.

Magento Websites

Lists all websites.

List Cronjobs

Lists all cronjobs defined in crontab.xml files.

Run Cronjobs

Runs a cronjob by code.

If no job argument is passed you can select a job from a list. See it in action: http://www.youtube.com/watch?v=QkzkLgrfNaM If option schedule is present, cron is not launched, but just scheduled immediately in magento crontab.

Kill a running job

If no job is specified a interactive selection of all running jobs is shown. Jobs can only be killed if the process runs on the same machine as n98-magerun2.

Default timeout of a process kill is 5 seconds.

Cronjob History

Last executed cronjobs with status.

Create app/etc/env.php

Create env file interactively. If can also update existing files. To update a single value you can use the command config:env:set.

Set single value in env.php file

Set a single value in env.php by providing a key and an optional value. The command will save an empty string as default value if no value is set.

Sub-arrays in config.php can be specified by adding a "." character to every array.

You can also choose to provide a json text argument as value, by using the optional --input-format=json flag. This will allow you to add values that aren't a string but also other scalar types.

Examples:

Delete key from env.php file

Remove a configuration from the env.php file by providing a key.

Sub-arrays in config.php can be specified by adding a "." character to every array.

Examples:

Show env.php settings

If no key is passed, the whole content of the file is displayed as table.

Examples:

Config Search

Search in the store config meta data (labels). The output is a table with id, type and name of the config item.

Type can be one of:

• section
• group
• field

Set Store Config

Arguments:

• path - The config path value The config value

Options:

Get Store Config

Arguments:

• path - The config path

Options:

Help:

If path is not set, all available config items will be listed. path may contain wildcards (*)

Example:

Delete Store Config

Arguments:

• path - The config path

Options:

Display ACL Tree

Help:

Prints acl.xml data as table

Print Dependency Injection Config Data

Arguments:

• type - Type (class)

Options:

Print MView Config

Print the data of all merged mview.xml files.

Options:

Print Indexer Config

Print the data of all merged indexer.xml files.

Options:

List Magento cache status

Clean Magento cache

Cleans expired cache entries.

If you would like to clean only one cache type:

If you would like to clean multiple cache types at once:

If you would like to remove all cache entries use cache:flush

Run cache:list command to see all codes.

Remove all cache entries

Keep in mind that cache:flush cleares the cache backend, so other cache types in the same backend will be cleared as well.

Remove entry by ID

The command is not checking if the cache id exists. If you want to check if the cache id exists use the cache:remove:id command with the --strict option.

List Magento caches

Disable Magento cache

If no code is specified, all cache types will be disabled. Run cache:list command to see all codes.

Enable Magento cache

Cache Report

This command let you investigate what's stored inside your cache. It prints out a table with cache IDs.

Cache View

Prints stored cache entry by ID.

If value is serialized you can force a pretty output with --unserialize option. Some entries are encrypted and can be decrypted with --decrypt option. The command uses the core cache by default. If the FPC cache should be used, the --fpc option can be used.

Flush Catalog Images Cache

Removes pre-generated catalog images and triggers clean_catalog_images_cache_after event which should invalidate the full page cache.

If no code is specified, all cache types will be enabled. Run cache:list command to see all codes.

List admin users

Change admin user password

Delete admin user

ID can be e-mail or username. The command will attempt to find the user by username first and if it cannot be found it will attempt to find the user by e-mail. If ID is omitted you will be prompted for it. If the force parameter -f is omitted you will be prompted for confirmation.

Create Admin Token for Webapi

Run a raw DB query

Example:

Open MySQL Console

Options:

Dump database

Dumps configured Magento database with mysqldump.

• Requires MySQL CLI tools

Arguments:

• filename - Dump filename

Options:

Only the mysqldump command:

Or directly to stdout:

Use compression (gzip cli tool has to be installed):

Stripped Database Dump

Dumps your database and excludes some tables. This is useful for development or staging environments where you may want to provision a restricted database.

Separate each table to strip by a space. You can use wildcards like * and ? in the table names to strip multiple tables. In addition, you can specify pre-defined table groups, that start with an @ sign.

Example: dataflow_batch_export unimportant_module_* @log

Available Table Groups:

Import database

• Requires MySQL CLI tools

Arguments:

• filename - Dump filename

Options:

Fix empty authorization tables

If you run db:dump with stripped option and @admin group, the authorization_rule and authorization_role tables are empty. This blocks the creation of admin users.

You can re-create the default entries by running the command:

If you are using the db:import command to import the stripped SQL dump, then this command will be implicitly called.

Clear static view files

Options:

To clear assets for all themes:

To clear assets for specific theme(s) only:

List Themes

Create Module Skeleton

Creates an empty module and registers it in current Magento shop.

Detect Composer Dependencies in Module

The source code of one or more modules can be scanned for dependencies.

The --only-missing option will filter the output so that only the missing dependencies are listed.

Enable/disable inline translation feature for Magento Admin:

Enable/disable inline translation feature for shop frontend:

Set a translation (saved in translation table)

Export inline translations

List modules

Lists all installed modules. If --vendor option is set, only modules of the given vendor are listed. If --only-enabled option is set, only enabled modules are listed. If --only-disabled option is set, only disabled modules are listed. Format can be csv, json, xml or yaml.

Encryption

Encrypt the given string using Magentos crypt key

Decrypt the given string using Magentos crypt key

List Observers

List Routes

EAV Attributes

View the data for a particular attribute:

Generate Gift Card Pool

Generates a new gift card pool.

Create a Gift Card

You may specify a website ID or use the default. You may also optionally add an expiration date to the gift card using the --expires option. Dates should be in YYYY-MM-DD format.

View Gift Card Information

Remove a Gift Card

Compare Setup Versions

Compares module version with saved setup version in setup_module table and displays version mismatchs if found.

• If a filename with --log-junit option is set the tool generates an XML file and no output to stdout.

Change Setup Version

Changes the version of a module. This command is useful if you want to re-run an upgrade script again possibly for debugging. Alternatively you would have to alter the row in the database manually.

Downgrade Setup Versions

Downgrade the versions in the database to the module version from its xml file if necessary. Useful while developing and switching branches between module version changes.

Dump Media folder

Creates a ZIP archive with media folder content.

Integrations (Webapi Access Tokens)

There are four commands to create, show, list, delete integrations (access tokens). This commands are very useful for developers.

List all existing integrations

Create a new integration

n98-magerun2.phar integration:create [options] [--] <name> [<email> [<endpoint>]]

Options:

If no ACL resource is defined the new integration token will be created with FULL ACCESS.

If you do not want that, please provide a list of ACL resources by using the --resource option.

Example:

n98-magerun2.phar integration:create "My new integration 10" [email protected] https://example.com -r Magento_Catalog::catalog_inventory -r Magento_Backend::system_other_settings

To see all available ACL resources, please run the command config:data:acl.

Show infos about existing integration

n98-magerun2.phar integration:show --format[=FORMAT] <name_or_id> [key]

Example (print only Access Key):

n98-magerun2.phar integration:show 1 "Access Key"

Delete integration

n98-magerun2.phar integration:delete <name_or_id>

Github

(experimental) Commands

Pull Requests

Gets infos about Github Pull Requests. If no Github Repository is defined by ---repository (-r) option the default Magento 2 Github Repository magento/magento2 is used. For the Mage-OS repository we provide a shortcut option --mage-os.

If the command is executed without any options it will show infos about the PR.

# Magento 2 Open Source
n98-magerun2.phar github:pr:patch <pr-number>

# Mage-OS
n98-magerun2.phar github:pr:patch --mage-os <pr-number>

Create a patch file from PR:

n98-magerun2.phar github:pr:patch --patch <pr-number>

Files of the magento2-base and magento2-ee-base and b2b base packages are currently not handled by the command.

List only the raw diff:

n98-magerun2.phar github:pr:patch --diff <pr-number>

Interactive Development Console

Opens PHP interactive shell with initialized Magento Admin-Store.

n98-magerun2.phar dev:console [--area=AREA] <arg>

Optional an area code can be defined. If provided, the configuration (di.xml, translations) of the area are loaded.

Possible area codes are:

• adminhtml
• crontab
• frontend
• graphql
• webapi_xml
• webapi_rest

Variable $di is made available with a Magento\Framework\ObjectManagerInterface instance to allow creation of object instances.

Variable $dh provides convenient debugging functions. Type $dh-> and press Tab for a list.

Example:

n98-magerun2 dev:console --area=adminhtml
    // show name of category 123 in default store
    $dh->debugCategoryById(123)['name']; 
    // show name of product id 123
    $dh->debugProductById(123)['name']; 

The interactive console works as REPL. It's possible to enter any PHP code. The code will be executed immediately. The interactive console also comes with a lot of embedded scommands.

It's possible to add initial commands to the interactive console. Commands should be delimited by a semicolon. You can mix PHP-Code with embedded interactive console commands.

Example:

n98-magerun2.phar dev:console "$a = 1; call cache:flush; ls;"

The interactive console comes with a extendable code generator tool to create i.e. modules, cli commands, controllers, blocks, helpers etc.

The console can be in a module context which allows you to generate code for a selected module.

The basic idea of the stateful console was developed by Jacques Bodin-Hullin in this great tool Installer.

n98-magerun Script

Run multiple commands from a script file.

n98-magerun2.phar script [-d|--define[="..."]] [--stop-on-error] [filename]

Example:

# Set multiple config
config:store:set "web/cookie/cookie_domain" example.com

# Set with multiline values with `\n`
config:store:set "general/store_information/address" "First line\nSecond line\nThird line"

# This is a comment
cache:flush

Optionally you can work with unix pipes.

echo "cache:flush" | n98-magerun2.phar script

n98-magerun2.phar script < filename

It is even possible to create executable scripts:

Create file test.magerun and make it executable chmod +x test.magerun:

#!/usr/bin/env n98-magerun2.phar script

config:store:set "web/cookie/cookie_domain" example.com
cache:flush

# Run a shell script with "!" as first char
! ls -l

# Register your own variable (only key = value currently supported)
${my.var}=bar

# Let magerun ask for variable value - add a question mark
${my.var}=?

! echo ${my.var}

# Use resolved variables from n98-magerun in shell commands
! ls -l ${magento.root}/code/local

Pre-defined variables:

Variables can be passed to a script with "--define (-d)" option.

Example:

n98-magerun2.phar script -d foo=bar filename

# This will register the variable ${foo} with value bar.

It's possible to define multiple values by passing more than one option.

Environment variables can be used in a script by using the env. prefix.

Example:

!echo "My current working directory is: ${env.PWD}"
!echo "Path: ${env.PATH}"

Toggle CMS Block status

Toggles the status for a CMS block based on the given Block identifier.

n98-magerun2.phar cms:block:toggle [blockId]

Change Admin user status

Changes the admin user based on the options, the command will toggle the status if no options are supplied.

n98-magerun2.phar admin:user:change-status [user] [--activate] [--deactivate]

Note: It is possible for a user to exist with a username that matches the email of a different user. In this case the first matched user will be changed.

Add Sales Sequences for a given store

Create sales sequences in the database if they are missing, this will recreate profiles to.

n98-magerun2.phar sales:sequence:add [store] 

If store is omitted, it'll run for all stores.

Note: It is possible a sequence already exists, in this case nothing will happen, only missing tables are created.

Remove Sales Sequences for a given store

Remove sales sequences from the database, warning, you cannot undo this, make sure you have database backups.

n98-magerun2.phar sales:sequence:remove [store] 

If store is omitted, it'll run for all stores. When the option no-interaction is given, it will run immediately without any interaction. Otherwise it will remind you and ask if you know what you're doing and ask for each store you are running it on.

Note: .

Script Repository

You can organize your scripts in a repository. Simply place a script in folder /usr/local/share/n98-magerun2/scripts or in your home dir in folder <HOME>/.n98-magerun2/scripts.

Scripts must have the file extension .magerun.

After that you can list all scripts with the script:repo:list command. The first line of the script can contain a comment (line prefixed with #) which will be displayed as description.

n98-magerun2.phar script:repo:list [--format[="..."]]

If you want to execute a script from the repository this can be done by script:repo:run command.

n98-magerun2.phar script:repo:run [-d|--define[="..."]] [--stop-on-error] [script]

Script argument is optional. If you don't specify any you can select one from a list.

Composer Redeploy Base Packages

If files are missing after a Magento updates it could be that new files were added to the files map in the base packages of Magento. The composer:redeploy-base-packages command can fix this issue.

n98-magerun2.phar composer:redeploy-base-packages

Development

https://github.com/netz98/n98-magerun2/wiki