Adobe Commerce Operations

https://experienceleague.adobe.com/en/docs/commerce-operations
Admin
Adobe Commerce Operations documentation provides comprehensive guides for configuring, implementing,...
Tokens:854,818
Snippets:9,283
Trust Score:10
Update:7 months ago
Show doc for...
Tokens:
Raw
### Example: Get Help for 'setup:install' Command (bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/composer

Demonstrates how to use the `help` command to get specific information about the `setup:install` command in Adobe Commerce. This helps users understand the prerequisites and steps for installing the application.

```bash
bin/magento help setup:install
```

--------------------------------

### Magento Queue Consumer Start Examples (Shell)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/tools/cli-reference/commerce-on-premises

Provides practical examples of using the `bin/magento queue:consumers:start` command with different configurations. These examples demonstrate how to start a consumer, limit message processing, set batch sizes, specify an area code, run in single-thread mode, and configure multi-processing.

```shell
bin/magento queue:consumers:start someConsumer
bin/magento queue:consumers:start someConsumer --max-messages=50
bin/magento queue:consumers:start someConsumer --batch-size=500
bin/magento queue:consumers:start someConsumer --area-code='adminhtml'
bin/magento queue:consumers:start someConsumer --single-thread
bin/magento queue:consumers:start someConsumer --pid-file-path='/var/someConsumer.pid'
bin/magento queue:consumers:start someConsumer --multi-process=4
```

--------------------------------

### Install Magento with Setup Command (Bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/tools/cli-reference/commerce-on-premises

The `setup:install` command in Magento is used to install the application. It supports a wide array of options to configure database connections, caching mechanisms (including Redis), session storage, remote storage drivers, and other essential setup parameters. This command is fundamental for initializing a new Magento environment.

```bash
bin/magento setup:install [--remote-storage-driver REMOTE-STORAGE-DRIVER] [--remote-storage-prefix REMOTE-STORAGE-PREFIX] [--remote-storage-endpoint REMOTE-STORAGE-ENDPOINT] [--remote-storage-bucket REMOTE-STORAGE-BUCKET] [--remote-storage-region REMOTE-STORAGE-REGION] [--remote-storage-key REMOTE-STORAGE-KEY] [--remote-storage-secret REMOTE-STORAGE-SECRET] [--remote-storage-path-style REMOTE-STORAGE-PATH-STYLE] [--backend-frontname BACKEND-FRONTNAME] [--enable-debug-logging ENABLE-DEBUG-LOGGING] [--enable-syslog-logging ENABLE-SYSLOG-LOGGING] [--id_salt ID_SALT] [--checkout-async CHECKOUT-ASYNC] [--config-async CONFIG-ASYNC] [--amqp-host AMQP-HOST] [--amqp-port AMQP-PORT] [--amqp-user AMQP-USER] [--amqp-password AMQP-PASSWORD] [--amqp-virtualhost AMQP-VIRTUALHOST] [--amqp-ssl AMQP-SSL] [--amqp-ssl-options AMQP-SSL-OPTIONS] [--consumers-wait-for-messages CONSUMERS-WAIT-FOR-MESSAGES] [--queue-default-connection QUEUE-DEFAULT-CONNECTION] [--deferred-total-calculating DEFERRED-TOTAL-CALCULATING] [--key KEY] [--db-host DB-HOST] [--db-name DB-NAME] [--db-user DB-USER] [--db-engine DB-ENGINE] [--db-password DB-PASSWORD] [--db-prefix DB-PREFIX] [--db-model DB-MODEL] [--db-init-statements DB-INIT-STATEMENTS] [-s|--skip-db-validation] [--http-cache-hosts HTTP-CACHE-HOSTS] [--db-ssl-key DB-SSL-KEY] [--db-ssl-cert DB-SSL-CERT] [--db-ssl-ca DB-SSL-CA] [--db-ssl-verify] [--session-save SESSION-SAVE] [--session-save-redis-host SESSION-SAVE-REDIS-HOST] [--session-save-redis-port SESSION-SAVE-REDIS-PORT] [--session-save-redis-password SESSION-SAVE-REDIS-PASSWORD] [--session-save-redis-timeout SESSION-SAVE-REDIS-TIMEOUT] [--session-save-redis-retries SESSION-SAVE-REDIS-RETRIES] [--session-save-redis-persistent-id SESSION-SAVE-REDIS-PERSISTENT-ID] [--session-save-redis-db SESSION-SAVE-REDIS-DB] [--session-save-redis-compression-threshold SESSION-SAVE-REDIS-COMPRESSION-THRESHOLD] [--session-save-redis-compression-lib SESSION-SAVE-REDIS-COMPRESSION-LIB] [--session-save-redis-log-level SESSION-SAVE-REDIS-LOG-LEVEL] [--session-save-redis-max-concurrency SESSION-SAVE-REDIS-MAX-CONCURRENCY] [--session-save-redis-break-after-frontend SESSION-SAVE-REDIS-BREAK-AFTER-FRONTEND] [--session-save-redis-break-after-adminhtml SESSION-SAVE-REDIS-BREAK-AFTER-ADMINHTML] [--session-save-redis-first-lifetime SESSION-SAVE-REDIS-FIRST-LIFETIME] [--session-save-redis-bot-first-lifetime SESSION-SAVE-REDIS-BOT-FIRST-LIFETIME] [--session-save-redis-bot-lifetime SESSION-SAVE-REDIS-BOT-LIFETIME] [--session-save-redis-disable-locking SESSION-SAVE-REDIS-DISABLE-LOCKING] [--session-save-redis-min-lifetime SESSION-SAVE-REDIS-MIN-LIFETIME] [--session-save-redis-max-lifetime SESSION-SAVE-REDIS-MAX-LIFETIME] [--session-save-redis-sentinel-master SESSION-SAVE-REDIS-SENTINEL-MASTER] [--session-save-redis-sentinel-servers SESSION-SAVE-REDIS-SENTINEL-SERVERS] [--session-save-redis-sentinel-verify-master SESSION-SAVE-REDIS-SENTINEL-VERIFY-MASTER] [--session-save-redis-sentinel-connect-retries SESSION-SAVE-REDIS-SENTINEL-CONNECT-RETRIES] [--cache-backend CACHE-BACKEND] [--cache-backend-redis-server CACHE-BACKEND-REDIS-SERVER] [--cache-backend-redis-db CACHE-BACKEND-REDIS-DB] [--cache-backend-redis-port CACHE-BACKEND-REDIS-PORT] [--cache-backend-redis-password CACHE-BACKEND-REDIS-PASSWORD] [--cache-backend-redis-compress-data CACHE-BACKEND-REDIS-COMPRESS-DATA] [--cache-backend-redis-compression-lib CACHE-BACKEND-REDIS-COMPRESSION-LIB] [--cache-backend-redis-use-lua CACHE-BACKEND-REDIS-USE-LUA] [--cache-backend-redis-use-lua-on-gc CACHE-BACKEND-REDIS-USE-LUA-ON-GC] [--cache-id-prefix CACHE-ID-PREFIX] [--allow-parallel-generation] [--page-cache PAGE-CACHE] [--page-cache-redis-server PAGE-CACHE-REDIS-SERVER] [--page-cache-redis-db PAGE-CACHE-REDIS-DB] [--page-cache-redis-port PAGE-CACHE-REDIS-PORT] [--page-cache-redis-password PAGE-CACHE-REDIS-PASSWORD] [--page-cache-redis-compress-data PAGE-CACHE-REDIS-COMPRESS-DATA] [--page-cache-redis-compression-lib PAGE-CACHE-REDIS-COMPRESSION-LIB] [--page-cache-id-prefix PAGE-CACHE-ID-PREFIX] [--lock-provider LOCK-PROVIDER]
```

--------------------------------

### Install Magento Commerce via CLI

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/advanced

This command executes the Magento setup process, configuring the database, administrative credentials, and search engine settings. It requires an OpenSearch host and port to be specified for successful search integration.

```bash
magento setup:install --base-url=http://127.0.0.1/magento2/ \
--db-host=localhost --db-name=magento --db-user=magento --db-password=magento \
--admin-firstname=Magento --admin-lastname=User --admin-email=user@example.com \
--admin-user=admin --admin-password=admin123 --language=en_US \
--currency=USD --timezone=America/Chicago --cleanup-database \
--sales-order-increment-prefix="ORD$" --session-save=db --use-rewrites=1 \
--search-engine=opensearch --opensearch-host=os-host.example.com \
--opensearch-port=9200
```

--------------------------------

### Start RabbitMQ Server (Bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/upgrade-guide/prepare/activemq-migration

Starts the RabbitMQ server using `systemctl`. This command requires root privileges (sudo) and assumes RabbitMQ is installed and managed by systemd. It ensures the message broker is running before proceeding.

```bash
sudo systemctl start rabbitmq-server
```

--------------------------------

### Install Adobe Commerce with Admin User

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/advanced

Executes the magento setup:install command with full configuration parameters including database credentials, search engine settings, and initial admin account details.

```bash
magento setup:install --db-host=localhost --db-name=magento --db-user=magento --db-password=magento \
--admin-firstname=Magento --admin-lastname=User --admin-email=user@example.com \
--admin-user=admin --admin-password=admin123 --language=en_US \
--currency=USD --timezone=America/Chicago --use-rewrites=1 \
--search-engine=opensearch --opensearch-host=os-host.example.com \
--opensearch-port=9200
```

--------------------------------

### Install Adobe Commerce via CLI

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/tutorials/install

The magento setup:install command is used to initialize the Adobe Commerce application. It accepts various options for database and site configuration, requiring specific admin credentials for versions 2.2.8 and later.

```bash
magento setup:install --<option>=<value> ... --<option>=<value>
```

--------------------------------

### CLI setup:db-declaration:generate-whitelist

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/tools/cli-reference/commerce-on-premises?lang=en

Generates a whitelist of tables and columns allowed for modification by the declaration installer.

```APIDOC
## [CLI] setup:db-declaration:generate-whitelist

### Description
Generates a whitelist of tables and columns that are allowed to be edited by the declaration installer.

### Method
CLI

### Endpoint
bin/magento setup:db-declaration:generate-whitelist

### Parameters
#### Options
- **--module-name** (string) - Optional - Name of the module where whitelist will be generated. Default: all

### Request Example
bin/magento setup:db-declaration:generate-whitelist --module-name=My_Module
```

--------------------------------

### Example: Get Help for 'cache:enable' Command (bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/composer

Illustrates how to obtain help for the `cache:enable` command within the Adobe Commerce CLI. This is useful for managing the application's cache and understanding its related options.

```bash
bin/magento help cache:enable
```

--------------------------------

### Install and Manage Firewalld Service

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/web-server/nginx

Installs the firewalld package using yum, starts the service, and enables it to persist across system reboots. This is required for network security management on the server.

```bash
yum -y install firewalld
systemctl start firewalld
systemctl enable firewalld
```

--------------------------------

### Example Dependency Count Output

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/performance-best-practices/concepts/advanced-js-bundling

This is an example output from the 'sort bundle/*.txt | uniq -c | sort -n' command, illustrating how dependencies are listed with their counts. The numbers indicate how many files contain each specific dependency.

```none
1 buildTools,
1 jquery/jquery.parsequery,
1 jsbuild,
2 jquery/jquery.metadata,
2 jquery/validate,
2 mage/bootstrap,
3 jquery
3 jquery/ui
3 knockoutjs/knockout
...
```

--------------------------------

### Install Adobe Commerce with Remote Storage (Bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/storage/remote-storage/remote-storage

Installs Adobe Commerce with remote storage enabled. Requires specifying the storage driver, bucket name, and region. Uses the `setup:install` CLI command.

```bash
bin/magento setup:install --remote-storage-driver="aws-s3" --remote-storage-bucket="myBucket" --remote-storage-region="us-east-1"
```

--------------------------------

### Install Adobe Commerce without Admin User

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/advanced

Executes the magento setup:install command without specifying admin credentials. This is useful for automated deployments where the administrator account is created in a subsequent step.

```bash
magento setup:install --base-url=http://127.0.0.1/magento2/ \
--db-host=localhost --db-name=magento --db-user=magento --db-password=magento \
--language=en_US --currency=USD --timezone=America/Chicago --use-rewrites=1 \
--search-engine=opensearch --opensearch-host=os-host.example.com \
--opensearch-port=9200
```

--------------------------------

### setup:static-content:deploy

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/tools/cli-reference/commerce-on-premises?lang=en

Deploys static view files for specified languages, themes, and areas.

```APIDOC
## CLI COMMAND: setup:static-content:deploy

### Description
Deploys static view files to the pub/static directory.

### Method
CLI

### Endpoint
bin/magento setup:static-content:deploy [<languages>...]

### Parameters
#### Arguments
- **languages** (array) - Optional - Space-separated list of ISO-639 language codes

#### Options
- **--force, -f** (boolean) - Optional - Deploy files in any mode
- **--strategy, -s** (string) - Optional - Deploy strategy (Default: quick)
- **--jobs, -j** (integer) - Optional - Number of parallel jobs
- **--content-version** (string) - Optional - Custom version for multi-node deployment

### Request Example
bin/magento setup:static-content:deploy en_US en_GB
```

--------------------------------

### Install Dependencies with Composer

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/deployment/build-system

Executes the composer install command to download and set up all required project dependencies defined in the composer.json file. This is a prerequisite for environment initialization.

```bash
composer install
```

--------------------------------

### Global Options (Example: --maxWaitTime)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/tools/cli-reference/commerce-on-premises?lang=en

Demonstrates how global options like `--maxWaitTime` can be applied to various commands.

```APIDOC
## Global Options Example: `--maxWaitTime`

### Description
Controls how long to wait for workers after a reload (e.g., config change) before killing them.

### Method
Applies to various commands (e.g., `server:state-monitor:aggregate-output`)

### Endpoint
N/A (Global Option)

### Parameters
#### Query Parameters
* `--maxWaitTime` or `-mwt` (integer) - Optional - How long to wait for workers after reload (e.g., config change) before killing them. (Default: `3600`)

### Request Example (applied to `server:state-monitor:aggregate-output`)
```bash
bin/magento server:state-monitor:aggregate-output --maxWaitTime 7200
```

### Response
(Response depends on the command the option is applied to)
#### Success Response (200)
(Response depends on the command the option is applied to)

#### Response Example
(Response depends on the command the option is applied to)
```

--------------------------------

### Database and Sample Data Options

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/tools/cli-reference/commerce-on-premises-beta

Controls database cleanup before installation and whether to use sample data. These options help in setting up a clean or pre-populated environment.

```bash
# Example usage:
# --cleanup-database
# --use-sample-data
```

--------------------------------

### GET setup:db:status

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/tools/cli-reference/commerce-on-premises?lang=en

Checks the current state of the database to determine if schema or data upgrades are required.

```APIDOC
## GET setup:db:status

### Description
Checks if the database schema or data requires an upgrade.

### Method
GET

### Endpoint
bin/magento setup:db:status

### Parameters
#### Query Parameters
- **--magento-init-params** (string) - Optional - Customizes Magento initialization parameters (e.g., MAGE_MODE=developer).

### Request Example
bin/magento setup:db:status --magento-init-params "MAGE_MODE=developer"

### Response
#### Success Response (200)
- **status** (string) - Indicates whether the database is up to date or requires an upgrade.
```

--------------------------------

### Sample Output for STORE_WEBSITE Table

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/paths/override-config-settings

This is a sample output from querying the `STORE_WEBSITE` table, illustrating the structure and data typically found, including website ID, code, name, and default settings.

```shell
mysql> SELECT * FROM STORE_WEBSITE;
+------------+------+--------------+------------+------------------+------------+
| website_id | code | name         | sort_order | default_group_id | is_default |
+------------+------+--------------+------------+------------------+------------+
|          0 | admin | Admin        |          0 |                0 |          0 |
|          1 | base  | Main Website |          0 |                1 |          1 |
+------------+------+--------------+------------+------------------+------------+
```

--------------------------------

### Sample Store Website Data (SQL Output)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/configuration-management/set-configuration-values

This section displays a sample output from a SQL query against the `store_website` table. It illustrates the structure and content of the data, including columns like `website_id`, `code`, `name`, `sort_order`, `default_group_id`, and `is_default`. This is a representation of data, not executable code.

```text
[mysql]> SELECT * FROM store_website;
+------------+------+- --------------+------------+------------------+------------+
| website_id | code | name         | sort_order | default_group_id | is_default |
+------------+------+- --------------+------------+------------------+------------+
|          0 | admin | Admin        |          0 |                0 |          0 |
|          1 | base  | Main Website |          0 |                1 |          1 |
|          2 | test1 | Test Website |          0 |                3 |          0 |
+------------+------+- --------------+------------+------------------+------------+
```

--------------------------------

### Configure Elasticsearch Port

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/web-server/nginx

Sets the Elasticsearch service port to 9200. This is a configuration parameter typically used during the installation or setup phase of the Adobe Commerce search engine integration.

```bash
--elasticsearch-port=9200
```

--------------------------------

### Install Adobe Commerce via CLI

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/tutorials/install

This command initializes the Magento installation process. It configures the database, admin credentials, locale settings, and Elasticsearch 7 integration.

```bash
magento setup:install --base-url=http://127.0.0.1/magento2/ \
--db-host=localhost --db-name=magento --db-user=magento --db-password=magento \
--admin-firstname=Commerce --admin-lastname=User --admin-email=user@example.com \
--admin-user=admin --admin-password=admin123 --language=en_US \
--currency=USD --timezone=America/Chicago --cleanup-database \
--sales-order-increment-prefix="ORD$" --session-save=db --use-rewrites=1 \
--search-engine=elasticsearch7 --elasticsearch-host=es-host.example.com \
--elasticsearch-port=9200
```

--------------------------------

### Install Adobe Commerce with Database Configuration (Bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/web-server/nginx

This command initiates the Adobe Commerce setup installation process via the command line. It requires specifying database connection details such as host, name, user, and password. Ensure these parameters are correctly configured for your environment.

```bash
bin/magento setup:install \
--db-host=localhost \
--db-name=magento \
--db-user=magento \
--db-password=magento
```

--------------------------------

### Install Adobe Commerce Application (bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/composer

Initiates the installation process for the Adobe Commerce application. This command requires no specific prerequisites and is the first step in setting up a new instance.

```bash
magento setup:install
```

--------------------------------

### Start GraphQL Application Server (bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/performance-best-practices/concepts/application-server

This command initiates the GraphQL Application Server, which acts as an HTTP proxy for GraphQL queries on port 9501. It's a key step in setting up the GraphQL environment.

```bash
bin/magento server:run
```

--------------------------------

### setup:db-declaration:generate-whitelist

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/tools/cli-reference/commerce-on-premises-beta

Generates a whitelist of tables and columns that are allowed to be edited by the declaration installer. This can be done for a specific module or all modules.

```APIDOC
## bin/magento setup:db-declaration:generate-whitelist

### Description
Generate whitelist of tables and columns that are allowed to be edited by declaration installer

### Method
`bash`

### Endpoint
`bin/magento setup:db-declaration:generate-whitelist [--module-name [MODULE-NAME]]`

### Parameters
#### Query Parameters
- **--module-name** (string) - Optional - Name of the module where whitelist will be generated. Default: `all`
```

--------------------------------

### Initialize MySQL Database for Memcache Testing

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/storage/session-storage/memcache-centos

Commands to create the database, user permissions, and sample table structure required for the Memcache test. This setup ensures the PHP script has a valid data source to query.

```bash
mysql -u root -p
```

```sql
create database memcache_test;
GRANT ALL ON memcache_test.* TO memcache_test@localhost IDENTIFIED BY 'memcache_test';
use memcache_test;
create table example (id int, name varchar(30));
insert into example values (1, "new_data");
exit
```

--------------------------------

### Install/Upgrade Magento Product with Composer (Bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade

This command installs or upgrades a specified Magento product to a given version using Composer. It's essential for managing dependencies in Magento installations. The `<product>` argument must be either `product-community-edition` or `product-enterprise-edition` for on-premises setups.

```bash
composer require-commerce magento/<product> <version> --no-update [--interactive-root-conflicts] [--force-root-updates] [--help]
```

--------------------------------

### Install Adobe Commerce with ActiveMQ Artemis using CLI

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/advanced

This command executes the Adobe Commerce setup utility to install the application with specific database, admin, and ActiveMQ Artemis message broker configurations. It requires Adobe Commerce version 2.4.5 or higher to function correctly.

```bash
bin/magento setup:install --base-url=http://127.0.0.1/magento2/ \
--db-host=localhost --db-name=magento --db-user=magento --db-password=magento \
--admin-firstname=Magento --admin-lastname=User --admin-email=user@example.com \
--admin-user=admin --admin-password=admin123 --language=en_US \
--currency=USD --timezone=America/Chicago --use-rewrites=1 \
--search-engine=opensearch --opensearch-host=os-host.example.com \
--opensearch-port=9200 --stomp-host=localhost --stomp-port=61613 \
--stomp-user=artemis --stomp-password=artemis
```

--------------------------------

### Adobe Commerce Module Configuration Structure

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/files/deployment-files

Example of the config.php file structure in Adobe Commerce, which lists installed modules and their enabled/disabled status. A value of '1' indicates enabled, and '0' indicates disabled.

```php
return array (
  'modules' =>
  array (
    'Magento_Core' => 1,
    'Magento_Store' => 1,
    'Magento_Theme' => 1,
    'Magento_Authorization' => 1,
    'Magento_Directory' => 1,
    'Magento_Backend' => 1,
    'Magento_Backup' => 1,
    'Magento_Eav' => 1,
    'Magento_Customer' => 1,
    ...
  ),
);
```

--------------------------------

### Start Artemis Broker (Bash)

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/message-brokers/activemq

This snippet shows how to start the Artemis broker service. The command provided starts the broker in the foreground, which is useful for testing and debugging purposes. Further configuration might be needed for production environments to run as a background service.

```bash
# Start in foreground (for testing)
# Add command to start broker here
```

--------------------------------

### Manage PHP-FPM service lifecycle

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/web-server/nginx

Commands to start the PHP-FPM service immediately and configure it to launch automatically upon system boot. Requires systemd-based Linux distributions.

```bash
systemctl start php-fpm
systemctl enable php-fpm
```

--------------------------------

### Create and Populate Magento 2 Sample Module Directory

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/crons/custom-cron-tutorial

This process involves creating the target directory structure for a new module and copying the sample files from a source repository. It assumes the user has appropriate filesystem permissions and the sample module source files are available in the home directory.

```bash
mkdir -p /var/www/html/magento2/app/code/Magento/SampleMinimal
```

```bash
cp -r ~/magento2-samples/sample-module-minimal/* /var/www/html/magento2/app/code/Magento/SampleMinimal
```

--------------------------------

### Configure Nginx Proxy Server

Source: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/search-engine/configure-nginx

Creates an Nginx configuration file to listen on port 8080 and proxy requests to the local Elasticsearch health endpoint. This setup requires Nginx to be installed and configured with appropriate permissions.

```conf
server {
   listen 8080;
   location /_cluster/health {
      proxy_pass http://localhost:9200/_cluster/health;
   }
}
```
Tokens:
Raw