[email protected]

Added command import-db to the scripts list.

v1.3.0

What's New

• New command import-db!
  This command allows importing database dump in MySQL in a single command. You don't need to do basically anything manually anymore. magento-scripts will apply all necessary patches to ensure that the database will work with the current configuration!
  Documentation available here.
• start command received new option --import-db.
  It does the same thing as the import-db command but allows to import database dump during start.
  Documentation available here.
• When running cli command now will be printed in console available aliases and shortcuts so you don't forget them!
• Removed deprecation warning in cli command on macOS Catalina and newer.
• Improved PHP extensions version detection.
  Now, magento-scripts will correctly identify missing extensions for the project and if the existing extension version is not correct for the project will install the correct version.
  Our guide for working with PHP extensions!
• Now magento-scripts will validate the connection to MySQL before it starts running Magento setup.
  This eliminates the famous MySQL server has gone away error during the first install and start of the project.
  Also, this connection is used to setup Magento configurations for ElasticSearch, base URL and URL rewrites so the whole startup process received a speed boost.

Bug Fixes

• Fixed once and forever problem with tunability CMA project to start after system shut down without stopping CMA projects.

Miscellaneous

• Bumped XDebug version to 3.0.3.
• Added check for ElasticSearch port configuration.
• Improved support for Magento version picker. Magento 2.4.2 support is coming soon.
• Alpha versions now will be published on NPM using an alpha tag.
  To install an alpha version: npm i @scandipwa/magento-scripts@alpha

@scandipwa/[email protected]

This pre-release contains the following changes:

• magento-scripts will now strictly check PHP extensions defined in the configuration file and install the correct version.|
  Previously, to upgrade XDebug, for example, you had to manually disable the extension with PHPBrew.
• Now when running cli command, in the console will be printed message with available aliases, such as php, magento, composer, and shortcuts: m for magento and c for composer.
• Enabled OPCache (Temporarily).
• Improved support for Magento version picker. Magento 2.4.2 support is coming soon.
• Bumped XDebug version to 3.0.3. (Changelog)

@scandipwa/[email protected]

This pre-release contains the following changes:

• Update command now recognizes if a newer version is available but it is a pre-release alpha version.
• Updated MySQL container health-check command. Now it should report the correct heath state.
• Fixed type errors in a new setup with MySQL connection. #19

@scandipwa/[email protected]

This pre-release contains the following changes:

• Now magento-scripts will validate the connection to MySQL before it starts running Magento setup.
  This eliminates the famous MySQL server has gone away error during the first install and start of the project.
  Also, this connection is used to setup Magento configurations for ElasticSearch, base URL and URL rewrites so the whole startup process received a speed boost.
• Added check for ElasticSearch port configuration.
• Fixed once and forever problem with tunability CMA project to start after system shut down without stopping CMA projects.

Bug Fixes and Improvements

What is New

• Now magento-scripts can choose available ports not only if they are free on the system, but also if they are not used by other CMA instances.
  To enable this feature, set useNonOverlappingPorts property to true in config file.
• Configuration file for the cli command is now a template file that will be stored in the cache folder. This is needed if you are using a custom PHP version, rather default PHP version by magento-scripts, which currently is 7.4.13.

Bug Fixes

• Fixed inability for CMA project to start after the system is shut down without manually stopping CMA projects. #16

@scandipwa/[email protected]

This release contains the following changes:

• Now magento-scripts will choose available ports not only if they are free on the system, but also if they are not used by other CMA instances.
  No more app/etc/env.php file deletion of ports have changed while your project was offline during other projects development.
• Configuration file for cli command is now a template file that will be stored in the cache folder. This is needed if you are using custom PHP version, rather default PHP version by magento-scripts, which currently is 7.4.13.

Prefixes and automatic theme installation!

What is New

• 👏 Prefixes 👏
  Previously, if you have 2 folders with the same name in but located different places (for example /home/user/my-cma-app and /home/user/test/my-cma-app you might experience strange behaviour, like 404 errors in Nginx or failed to mount local volume: no such file or directory. Now, CMA will by default append a unique prefix to the docker container names and volume names which should prevent errors described previously from appearing and allow to smoothly running CMA in non-unique folder names.
  ⚠️ Since prefixes are enabled by default, you might encounter problems during the upgrading to the version. We recommend disabling prefixes if this is the case through the config file, set the prefix property to false.
• Automatic theme installation.
  Now if your Magento is not installed and you starting the CMA project, magento-scripts will try to detect if you already have a theme installed in composer.json or not, and if it is then it will automatically link it after startup is complete.

Bug Fixes

• If magento-scripts are out-of-date, console message said to run a command npm upgrade -g ${package name} even if a package is installed locally. Now it will print the correct command if a package is installed locally or globally.

Configuration file is here!

What's new

• Configuration file is finally here! 👏
  Now when running start command will be automatically created cma.js file inside your project root directory. This file contains Magento configuration, docker services configuration, host and SSL configuration.

  NOTE: If you are upgrading existing CMA project old Magento configuration from the file app-config.json will be converted to magento field in cma.js.

  More about the configuration file can be found in docs: https://docs.create-magento-app.com/getting-started/config-file.

• status command will now also display containers environment variables. Useful when you need to get MySQL credentials for example.

@scandipwa/[email protected]

This release fixes when linking theme CMA was choosing the wrong port for redis persistent query configuration.