Q: markshust/docker-magento vs using a custom Docker Compose setup for Magento?

markshust/docker-magento provides pre-configured services and automation scripts that save time and ensure consistency, whereas a custom setup offers more flexibility but requires manual configuration and maintenance of each service.

Q: How to enable Redis caching in docker-magento?

Redis is enabled by default on new installs. For existing projects, use Magento CLI commands like bin/magento setup:config:set --cache-backend=redis, with server set to 'redis', as detailed in the Redis section of the README.

Q: What causes the 'Project directory is not empty' error and how to fix it?

This error occurs after a failed install attempt leaves files in the src directory. Fix the initial issue, then run bin/removeall to clean up, delete the project folder, and recreate it before retrying, as explained in Misc Info.

Q: How to use LiveReload for Magento theme development in this setup?

Create a theme, add a LiveReload script via layout XML, run bin/setup-grunt to configure Grunt, then start bin/grunt watch. Install the LiveReload browser extension, and CSS changes will auto-reload without refresh.

Question 1

How to set up Xdebug with markshust/docker-magento in PhpStorm?

Accepted Answer

Enable Xdebug with bin/xdebug enable, then configure PhpStorm by adding a CLI interpreter from Docker Compose and setting up a remote debug server. The README includes detailed steps, such as browser extension setup and IDE key configuration for breakpoints.

Question 2

How to import an existing Magento database into docker-magento?

Accepted Answer

Use bin/mysqldump to export your database, then after setting up the project, run bin/mysql < backup.sql to import it. Update env.php with Docker MySQL credentials, and run bin/magento app:config:import to sync settings.

Question 3

markshust/docker-magento vs using a custom Docker Compose setup for Magento?

Accepted Answer

markshust/docker-magento provides pre-configured services and automation scripts that save time and ensure consistency, whereas a custom setup offers more flexibility but requires manual configuration and maintenance of each service.

Question 4

How to enable Redis caching in docker-magento?

Accepted Answer

Redis is enabled by default on new installs. For existing projects, use Magento CLI commands like bin/magento setup:config:set --cache-backend=redis, with server set to 'redis', as detailed in the Redis section of the README.

Question 5

What causes the 'Project directory is not empty' error and how to fix it?

Accepted Answer

This error occurs after a failed install attempt leaves files in the src directory. Fix the initial issue, then run bin/removeall to clean up, delete the project folder, and recreate it before retrying, as explained in Misc Info.

Question 6

How to use LiveReload for Magento theme development in this setup?

Accepted Answer

Create a theme, add a LiveReload script via layout XML, run bin/setup-grunt to configure Grunt, then start bin/grunt watch. Install the LiveReload browser extension, and CSS changes will auto-reload without refresh.

docker-magento

What is docker-magento?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions