Awesome

Magento 2 Kubernetes DevBox

• What You get
• How to install
  • Requirements
  • Installation steps
  • Default credentials and settings
  • Getting updates and fixes
• Day-to-day development scenarios
  • Access Magento
  • Reinstall Magento
  • Clear Magento cache
  • Switch between CE and EE
  • Sample data installation
  • Basic data generation
  • Use Magento CLI (bin/magento)
  • Debugging with XDebug
  • Connecting to MySQL DB
  • View emails sent by Magento
  • Accessing PHP and other config files
  • Upgrading Magento
  • Multiple Magento instances
  • Update Composer dependencies
  • Running Magento tests
• Environment configuration
  • Switch between PHP versions
  • Activating Varnish
  • Activating ElasticSearch
  • Redis for caching
  • Reset environment
  • Switch NodeJS Versions
• DevBox tests
• FAQ

What You get

:warning: This project is under development and may become official Magento DevBox in the future. There is also a DevBox for Magento Cloud.

It's expected that the Magento 2 project source code will be located and managed on the host to allow quick indexing of project files by IDE. All other infrastructure is deployed in kubernetes cluster on Minikube.

Current DevBox aims to support multi-service multi-instance deployment in one click. Multiple Magento projects should be installed in a single Kubernetes cluster and share resoruces. Each of the Magento projects may be deployed as a monolith or a set of services. The DevBox is optimized for development scenarios using local environment.

The environment also suitable for for Magento Commerce and Magento B2B development.

The project initialization script configures a complete development environment:

1. Configures all software necessary for Magento 2: Nginx, PHP 7.x, MySQL 5.6, Git, Composer, XDebug, Redis, Rabbit MQ, Varnish
2. Installs Magento 2 from Git repositories or Composer packages (can be configured via checkout_source_from option in etc/instance/config.yaml)

How to install

If you never used Kubernetes before, read the Kubernetes Docs first.

Requirements

The software listed below should be available in PATH (except for PHP Storm).

• Docker
• Minikube
• Helm
• VirtualBox
• Git - Ensure that SSH keys are generated and associated with your Github account. See how to check and how to configure, if not configured.<br /> :information_source: To obtain the codebase without cloning, just use the Magento 2 codebase instead of devbox-magento/magento2ce. Either method will produce a successful installation.<br />

• PHP Storm, optional but recommended. To get Helm support in PhpStorm make sure to get v2018.3+
• NFS server must be installed and running on *nix and OSX hosts; usually available, follow installation steps first

Installation steps

:information_source: In case of any issues during installation, please read FAQ section

1. Open terminal and change your directory to the one you want to contain Magento project. <!-- On Windows use Git Bash, which is available after Git installation.-->

2. Download or clone the project with DevBox configuration:

   :warning: Do not open it in PhpStorm until init_project.sh has completed PhpStorm configuration in the initialize project step below.

   git clone --recursive git@github.com:magento/magento2-kubernetes-devbox.git magento2-devbox
   

   Optionally, if you use private repositories on GitHub or download packages from the Magento Marketplace using Composer.

   1. Copy etc/composer/auth.json.dist to etc/composer/auth.json.
   2. Specify your GitHub token by adding "github.com": "your-github-token" to the github-oauth section for GitHub authorization.
   3. Add the Magento Marketplace keys for Marketplace authorization to the repo.magento.com section.
   4. Copy (optional) etc/instance/config.yaml.dist as etc/instance/<instance_name>.yaml and make the necessary customizations. Instance name is Magento instance identifier that can only include letters and numbers.
   5. Copy (optional) etc/env/config.yaml.dist as etc/env/config.yaml and make the necessary customizations.

3. Initialize the project (this will configure the environment, install Magento<!--, and configure the PHPStorm project-->):

   cd magento2-devbox
   
   # NFS configuration is needed just once for each project, it will prompt for your password to make changes on the host
   
   bash scripts/host/configure_nfs_exports.sh
   
   bash init_project.sh
   

   <!-- To initialize project with checkout container, clone sources to checkout directory and use -e parameter to init_project.sh call. ```bash bash init_project.sh -e ``` -->

4. Use the magento2-devbox directory as the project root in PHP Storm (not magento2-devbox/magento). This is important, because in this case PHP Storm will be configured automatically by init_project.sh.<!-- If NFS files sync is disabled in [config](etc/instance/config.yaml.dist) and on Windows hosts [verify the deployment configuration in PHP Storm](docs/phpstorm-configuration-windows-hosts.md).-->

   <!--Use the URL for accessing your Magento storefront in the browser as your Web server root URL. Typically this is the localhost, which refers to your development machine. Depending on how you've set up your VM you may also need a port number, like `http://localhost:8080`.-->

5. Configure the remote PHP interpreter in PHP Storm. Go to Preferences, then Languages and Frameworks. Click PHP and add a new remote interpreter. Select Deployment configuration as a source for connection details.

Default credentials and settings

Some of default settings are available for override. These settings can be found in the etc/instance/config.yaml.dist and etc/env/config.yaml.dist.

To override settings create a copy of etc/env/config.yaml.dist under the name 'config.yaml' and add your custom settings.

You can create multiple copies of etc/instance/config.yaml.dist, each of those copies will be responsible for a separate Magento instance deployed in the DevBox. Config file name must only include alpha-numeric characters and will be used to isolate instances (for instance domain name generation, DB name etc).

Upon a successful installation, you'll see the location and URL of the newly-installed Magento 2 application in console.

Web access:

• Access storefront at http://magento.<instance_name> (can be found in etc/instance/<instance_name>.yaml)
• Access admin panel at http://magento.<instance_name>/admin/
• Magento admin user/password: admin/123123q
• Rabbit MQ control panel: run bash k-open-rabbitmq, credentials admin/123123q

:information_source: Your admin URL, storefront URL, and admin user and password are located in etc/instance/<instance_name>.yaml.

Codebase and DB access:

• Path to your Magento installation in the container is the same as on the host <!-- - Can be retrieved from environment variable: `echo ${DEVBOX_ROOT}/` --> <!-- -  On Windows hosts: `/var/www/magento`--> <!-- -  On Mac and \*nix hosts: the same as on host -->
• MySQL DB host:
  • inside the container: localhost
  • remotely: run minikube ip to get the IP and use port 30306
• MySQL DB name: magento_<instance_name>, magento_<instance_name>_integration_tests
• MySQL DB user/password: root:123123q

Codebase on host

• CE codebase: magento2-devbox/<instance_name>
• Magento Commerce codebase will be available if path to commerce repository is specified in etc/instance/<instance_name>.yaml: magento2-devbox/<instance_name>/magento2ee

Getting updates and fixes

Current devbox project follows semantic versioning so feel free to pull the latest features and fixes, they will not break your project. For example your current branch is 2.0, then it will be safe to pull any changes from origin/2.0. However branch 3.0 will contain changes backward incompatible with 2.0. Note, that semantic versioning is only used for x.0 branches (not for develop or master).

:information_source: To apply changes run bash k-upgrade-environment.

Day-to-day development scenarios

Access Magento

Use the following command to open current instance:

./m-open

Hostname can also be found in magento/host_name section of etc/instance/<instance_name>.yaml.

Reinstall Magento

Use commands described in Switch between CE and EE section with -f flag. Before doing actual re-installation, these commands update linking of EE codebase, clear cache, update composer dependencies.

If no composer update and relinking of EE codebase is necessary, use the following command. It will clear Magento DB, Magento caches and reinstall Magento instance.

Go to the root of the project in command line and execute:

./m-reinstall

Clear Magento cache

Go to the root of the project in command line and execute:

./m-clear-cache

Switch between CE and EE

Assume, that EE codebase is available in magento2-devbox/magento/magento2ee. The following commands will link/unlink EE codebase, clear cache, update composer dependencies and reinstall Magento. Go to 'magento2-devbox' created earlier and run in command line:

./m-switch-to-ce
# OR
./m-switch-to-ee

Force switch can be done using -f flag even if already switched to the target edition. May be helpful to relink EE modules after switching between branches.

Upgrade can be performed instead of re-installation using -u flag.

Sample data installation

To install Magento with sample data using Git:

1. Uncomment the sample data repository link at additional_repositories in etc/instance/<instance_name>.yaml. To ensure the yaml file can be correctly parsed, only remove the # and the space afterwards.
2. Run ./m-switch-to-ce -f or ./m-switch-to-ee -f, depending on the edition to be installed. To disable sample data, comment out additional repositories and force-switch to necessary edition (using the same commands).

If sample data is not showing, try the following:

1. Navigate to the magento2-devbox/<instance_name> directory such as magento2-devbox/default.
2. Run git clone git@github.com:magento/magento2-sample-data.git or git@github.com:magento/magento2-sample-data-ee.git depending on the edition to be installed.
3. Navigate back up to the magento2-devbox directory.
4. Run ./m-switch-to-ce -f or ./m-switch-to-ee -f, depending on the edition to be installed.

To install Magento with sample data using Composer:

Follow the steps outlined here.

Basic data generation

Several entities are generated for testing purposes by default using REST API after Magento installation:

• Customer with address (credentials customer@example.com:123123qQ)
• Category
• Couple simple products
• Configurable product

To disable this feature, set magento/generate_basic_data in etc/instance/<instance_name>.yaml to 0 and run ./m-switch-to-ce -f or ./m-switch-to-ee -f, depending on the edition to be installed.

Use Magento CLI (bin/magento)

Go to 'magento2-devbox' created earlier and run in command line:

./m-bin-magento <command_name>
# e.g.
./m-bin-magento list

Debugging with XDebug

XDebug is already configured to connect to the host machine automatically. So just:

1. Set XDEBUG_SESSION=1 cookie (e.g. using 'easy Xdebug' extension for Firefox). See XDebug documentation for more details
2. Start listening for PHP Debug connections in PhpStorm on default 9000 port. See how to integrate XDebug with PhpStorm
3. Set beakpoint or set option in PhpStorm menu 'Run -> Break at first line in PHP scripts'

Connecting to MySQL DB

Go to 'magento2-devbox' created earlier and run in command line:

bash k-ssh-mysql

After successful login to the container run the following command and enter 123123q when prompted for a password:

mysql -uroot -p

To connect remotely run minikube ip to get the IP and use port 30306

View emails sent by Magento

Not available yet.

Accessing PHP and other config files

The following configuration files are used by default:

• NGINX
• PHP-FPM: ini, conf
• xDebug
• Dockerfile for monolith base image
• Actually applied Dockerfile for monolith with customizations
• Actually applied Dockerfile for monolith with xDebug and customizations
• Kubernetes config for Monolith
• Kubernetes Helm variables

Upgrading Magento

Sometimes it is necessary to test upgrade flow. This can be easily done as follows (assuming that you have installed instance):

• For git-based installation - check out codebase corresponding to the target Magento version. Or modify your composer.json in case of composer-based installation
• Use commands described in Switch between CE and EE section with -u flag

Multiple Magento instances

Not available yet.

Update Composer dependencies

Go to 'magento2-devbox' created earlier and run in command line:

./m-composer install
# OR
./m-composer update

Running Magento tests

See how to run Magento tests from PhpStorm using remote PHP in Kubernetes cluster

Environment configuration

Switch between PHP versions

Not available yet.

Activating Varnish

Use the following commands to enable/disable varnish <!--without reinstalling Magento-->: m-varnish disable or m-varnish enable.

You can also set use_varnish: 1 in etc/env/config.yaml to use varnish. Changes will be applied on init_project.sh -f.

The VCL content can be found in configmap.yaml.

Activating ElasticSearch

Set search_engine: "elasticsearch" in etc/env/config.yaml to use ElasticSearch as current search engine or search_engine: "mysql" to use MySQL. Changes will be applied on m-reinstall.

Use the following commands to switch between search engines without reinstalling Magento: m-search-engine elasticsearch or m-search-engine mysql.

Redis for caching

Redis is configured as cache backend by default. <!--It is still possible to switch back to filesystem cache by changing `environment_cache_backend` to `filesystem` in [config.yaml](etc/instance/config.yaml.dist).-->

Reset environment

It is possible to reset project environment to default state, which you usually get just after project initialization. The following command will re-initialize Kubernetes cluster. Magento 2 code base (magento directory) and etc/instance/<instance_name>.yaml and PhpStorm settings will stay untouched<!--, but guest config files (located in [etc/guest](etc/guest)) will be cleared-->.

Go to 'magento2-devbox' created earlier and run in command line:

./init_project.sh -f

It is possible to reset Magento 2 code base at the same time. Magento 2 code base will be deleted and then cloned from the repositories specified in etc/config.yaml

./init_project.sh -fc

To reset PhpStorm project configuration, in addition to -f specify -p option:

./init_project.sh -fp

Ultimate project reset can be achieved by combining all available flags:

./init_project.sh -fcp

Switch NodeJS Versions

NodeJS not available yet.

DevBox tests

The tests are executed on every PR on Travis CI. It is possible to configure the same tests to run on the forked repository. In order to run composer-based Magento tests for the fork, repo.magento.com credentials must be set to COMPOSER_AUTH environment variable on Travis CI, the variable value should be:

'{"http-basic": {"repo.magento.com": {"username": "<public_key>","password": "<secret_key>"}}}'

An extended testsuite by default is executed against the master branch only. It is possible to execute an extended testsuite on every build by commenting out if: branch = master in the .travis.yaml

The same tests can be run on local using the following command. :warning: only one devbox can be running on the same host at the same time. The tests will destroy existing devbox installation.

cd tests
bash ./<test-name>.sh

FAQ

1. To debug any CLI script in current Devbox project, set debug:devbox_project option in etc/env/config.yaml to 1
2. Make sure that you used magento2-devbox directory as project root in PHP Storm (not magento2-devbox/magento)
3. If project opened in PhpStorm looks broken, close PhpStorm and remove magento2-devbox/.idea. Run ./magento2-devbox/scripts/host/configure_php_storm.sh. After opening project in PhpStorm again everything should look good
4. Please make sure that currently installed software, specified in requirements section, meets minimum version requirement
5. Be careful if your OS is case-insensitive, NFS might break the symlinks if you cd into the wrong casing and you power the devbox up. Just be sure to cd in to the casing the directory was originally created as.
6. Cannot run unit tests from PHPStorm on Magento 2.2, see possible solution here
7. Permission denied (publickey)
8. If you get minikube time out error restarting cluster while initializing project, run minikube stop && minikube delete && ./init_project.sh.
9. To modify the docker image used for php-fpm container:
   • Make changes in etc/docker/monolith/Dockerfile
   • Run ./k-upgrade-environment
   • Run ./k-status to open kubernetes dashboard and delete Replica Set named magento2-monolith-*. The container should be restarted and its Age should reset
10. If you face Input/output error command terminated with exit code 1 try to run the same command again, it will succeed after several trials.
11. The project was working initially, but Magento instance domain name stopped resolving. In some cases minikube IP may be changed, run ./scripts/host/configure_etc_hosts.sh