Open Ratnarashi opened 5 years ago
@Ratnarashi Which .htaccess did you change specifically and did you have to do anything else? I still get an error at ' Checking Component Dependency stage' after changing the few main ones.
@Ratnarashi Which .htaccess did you change specifically and did you have to do anything else? I still get an error at ' Checking Component Dependency stage' after changing the few main ones.
@Tenoke
After
docker-compose build
docker-compose up -d
And working through the Magento setup I then run,
docker-compose exec web sed -i -e "s/php_value memory_limit 756M/php_value memory_limit 2G/g" /var/www/html/.htaccess
This edits the .htaccess in the running container.
`docker-compose exec web apachectl -k graceful`
Restart apache.
`docker-compose exec -u www-data web php /var/www/html/bin/magento config:set system/backup/functionality_enabled 1`
Enable Magento's backup system.
`docker-compose exec -u www-data web rm -rf /generated/metadata/* /generated/code/*`
Clear out the generated files.
`docker-compose exec -u www-data web bin/magento deploy:mode:set developer`
Set developer mode to get error reporting
`docker-compose exec -u www-data web bin/magento cache:enable`
Enable the cache so that it runs at a decent speed.
I could then install the demo data using composer and install extensions from the market place.
Hope this helps.
Thank you, that worked flawlessly!
I have found that attempting to install any extension from the marketplace via the GUI fails the Readiness check at the Checking Component Dependency stage.
This is caused by PHP memory_limit being set in the .htaccess to 756M which is too low 2G is recommended.
I have had to sed my .htaccess to fix this issue.