Stratus - General Guides on Webscale Product Documentation

Stratus Guides - Backup Strategies

Mon, 01 Jan 0001 00:00:00 +0000

Backup to Amazon S3 Bucket

The AWS CLI comes preinstalled on Stratus. Run aws configure and follow the prompts entering the appropriate region and access key for your AWS account.

Example:

$ aws configure
AWS Access Key ID [None]: ABCDEFGHIJKLMNOPQRSTUVWXYZ
AWS Secret Access Key [None]: FaK3S3Cr3tAcc3SSK3yF0rFun
Default region name [None]: us-east-1
Default output format [None]: text

Run aws s3 ls to show your existing buckets and manage other AWS resources.

Stratus Guides - Debugging Cron Errors

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: All Magento 2 stores hosted on Webscale STRATUS are required to have installed the [MageMojo Cron extension](/docs/reference/stratus/guides/magento-2/magemojo-cron/ “MageMojo Magento 2 Cron extension information”/). This extension helps prevent many of the cron issues inherent with Magento 2.

Debugging Magento Cron Tasks

Magento has its own default cron that runs and executes internal jobs and schedules. The best way to confirm these are running is using the [n98-magerun(2) utility][1].

To confirm any jobs have ran recently, do the following:

Stratus Guides - Other CDNs

Mon, 01 Jan 0001 00:00:00 +0000

When using other proxy services you introduce routing complexities. A request to an environment will first route through your proxy provider’s edge location, then to the CloudFront edge location and on to the AWS home region.

In these cases, STRATUS has no control of the full request flow. Support becomes more difficult due to a lost of visibility and diagnostics for systems outside of Webscale STRATUS.

In some cases, these services develop technical issues of their own, from routing/request failures or customer misconfigurations. Adding the additional proxy increases latency on every request to your environment.

Stratus Guides - Rotating Magento Logs

Mon, 01 Jan 0001 00:00:00 +0000

To setup Logrotate to automatically rotate Magento logs:

Create a directory outside of the webroot to hold the config files:
```
 mkdir /srv/etc/
 mkdir /srv/etc/logrotate
```
Create a logrotate.conf file with the following content:
```
 /srv/public_html/var/log/*.log {
 su magemojo magemojo
 daily
 missingok
 rotate 30
 compress
 delaycompress
 notifempty
 olddir /srv/scaled/var/log/old/
 }
```
- su magemojo magemojo — Ensures that permissions stay correct
- daily – Run once a day at time set by cron job
- missingok — Don’t panic if empty
- rotate 30 — Retain for 30 days
- compress — Compress 2nd most recent file
- delaycompress — Do not compress newest rotated log
- notifempty — Do not rotate empty files
Add a [cron job](/docs/reference/stratus/control-panels/cron-panel/schedule/ “Cron Schedule Control Panel”/) to run once a day at the correct time:

Stratus Guides - Using Symlinks

Mon, 01 Jan 0001 00:00:00 +0000

Good Example:

env.php -> /srv/shared/app/etc/env.php

Bad Example:

env.php -> ../../../../env.php

Stratus Guides - Blackfire.io

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: XDebug and Blackfire can never be used together.

Log into a Blackfire.io account.
Set up an environment or profile to obtain a Server ID and Server Token. To get started, first make sure you have an account with Blackfire.io. Set up an environment or profile so that you have a Server ID and Server Token.
Go to the [PHP > Blackfire][2] Admin panel.
Enter the [information as indicated](/docs/reference/stratus/control-panels/php-panel/blackfire/ “Blackfire Control Panel”/).

Using the Chrome or Firefox browser extensions, start profiling the Webscale STRATUS site direct from a browser.

Stratus Guides - Using Xdebug

Mon, 01 Jan 0001 00:00:00 +0000

While a powerful tool, Xdebug can drastically slow down a store if used in production, even when not actively tracing or profiling anything. It is highly advised to not use Xdebug on a Production environment unless absolutely necessary.

Xdebug has a variety of settings. By default Xdebug is configured in Webscale STRATUS to cover most situations. There are three ways to use Xdebug:

Profiling — outputs cachegrind files on the Webscale STRATUS file system to evaluate request performance
Tracing — outputs trace files on the file system with full output of all function calls with function processing times
Debug — connects a local IDE via SSH tunnel on Webscale STRATUS to step through code when called via browser request

Setup

Install the Chrome extension to trigger the profiling and tracing in Xdebug.

Stratus Guides - Configuring RabbitMQ

Mon, 01 Jan 0001 00:00:00 +0000

Consumers

To see a list of available consumers that you can set to run, use:

php bin/magento queue:consumers:list

Please note the following:

In a production environment the host will be rabbitmq
In a development environment the host will be 0.0.0.0, unless Autoscaling is enabled then the host will remain rabbitmq.

Below is an example configuration of the env.php file.

'cron_consumers_runner' => [
 'cron_run' => true,
 'max_messages' => 0,
 'consumers' => [
 'async.operations.all',
 'codegeneratorProcessor',
 'product_action_attribute.update',
 'product_action_attribute.website.update',
 'exportProcessor'
 ]
 ],
 'queue' => [
 'amqp' => [
 'host' => 'rabbitmq',
 'port' => '5672',
 'user' => 'username',
 'password' => 'yb2sovjbaa4atsbbn0s0ccm9uddekh6i',
 'virtualhost' => '/',
 'ssl' => 'false',
 'ssl_options' => []
 ]
 ],

A simple one-line command to add RabbitMQ queue to env.php file is:

Stratus Guides - Node.js Node Version Manager

Mon, 01 Jan 0001 00:00:00 +0000

Documentation for NVM can be found in Github .

Helpful Commands

To show available versions:
```
 $ nvm ls-remote
```
To install a specific version:
```
 $ nvm install v13.10.0
```
To confirm installed versions:
```
 $ node -v
 v14.2.0

 $ npm -v
 6.14.4
```
To switch through installed versions nvm provides the nvm use command. This works similarly to the install command.

For example, to switch to Node.js version 13.6.0:

Stratus Guides - Updating Base URLs

Mon, 01 Jan 0001 00:00:00 +0000

Base URLs are one of the most important parts of Magento and they can cause serious trouble if not entered correctly. The following is a remedy you can use to easily correct Base URLs that have been incorrectly entered.

Within the Magento Admin, Base URLs exist within the Stores > Configuration > General > Web panel.

Note that only two fields have an actual URL, the rest have placeholder variables that file in the domain automatically. This is typical of every Magento install, though some configurations have custom media/skin/js values for use with CDNs or other customizations.

Stratus Guides - Multistore Subfolder Configuration Method

Mon, 01 Jan 0001 00:00:00 +0000

Create the desired folder within the /pub/ directory in your root directory (for this example, we will use “en”). mkdir /srv/public_html/pub/en
Create the required symlinks within the new folder. Make sure they are absolute to prevent any issues with [autoscaling](/docs/reference/stratus/control-panels/autoscaling/ “Autoscaling control panel”/). For example:

cd /srv/public_html/pub/en ln -s /srv/public_html/app app

Once completed, the `/en` directory should appear like this:

	lrwxrwxrwx 1 www www 10 Mar 23 14:07 app -> /srv/public_html/app/
	lrwxrwxrwx 1 www www 19 Mar 23 14:08 index.php -> /srv/public_html/pub/index.php
	lrwxrwxrwx 1 www www 10 Mar 23 14:08 lib -> /srv/public_html/lib/
	lrwxrwxrwx 1 www www 27 Mar 23 17:13 media -> /srv/public_html/pub/media/
	lrwxrwxrwx 1 www www 28 Mar 23 17:13 static -> /srv/public_html/pub/static/
	lrwxrwxrwx 1 www www 10 Mar 23 14:08 var -> /srv/public_html/var/

Add the following code to the [Nginx includes](/docs/reference/stratus/control-panels/nginx-panel/includes/ “Nginx Includes control panel”/). Adjust the subfolder name, “/en”, in each occurence (7) to the actual subfolder you prefer, and the store code, “en_store_view”, in the one occurence.

`location /en/ { index index.php index.html index.htm; try_files $uri $uri/ /en/index.php?$args ; location ~* .php$ { expires off; fastcgi_pass php-fpm; fastcgi_keep_conn on; fastcgi_buffer_size 128k; fastcgi_buffers 4 256k;