himani_219 → created an issue.
"You can try a few optimizations to reduce memory usage during install_config_import_batch. First, increasing the memory_limit in php.ini might help handle large configurations. Another option is reducing the batch size in core/lib/Drupal/Core/Batch/BatchStorage.php to process smaller chunks at a time, which lowers peak memory consumption. If skipping the config import during installation is feasible, you could install the site with a minimal profile and then run drush cim after installation to handle the import separately. Additionally, temporarily disabling non-essential modules during installation and enabling garbage collection (gc_enable()) before the batch process starts can help free up memory.
"Hey, I ran into a similar issue before, and in my case, it was related to DDEV's docroot configuration. Could you check your .ddev/config.yaml file and make sure docroot is set correctly? For a standard Drupal setup, it should be docroot: web. If it's misconfigured, the web server might not be able to locate index.php, causing a 403 error.
Also, after making any changes, try running ddev restart to apply them. If that doesn’t help, could you confirm whether your web directory (or the appropriate docroot) actually contains index.php? That file is essential for serving Drupal.
If the issue persists, you might want to check out the DDEV troubleshooting guide (https://ddev.readthedocs.io/en/stable/users/usage/troubleshooting/)
himani_219 → created an issue.