Seravo / wordpress

The WordPress project layout used by many of Seravo's customers, suitable also for local development with Vagrant and git deployment
https://seravo.com
GNU General Public License v3.0
104 stars 53 forks source link

wp-pull-production fails because of memory_limit even if memory_limit would be set higher in php.ini #183

Open marttihyvonen opened 3 years ago

marttihyvonen commented 3 years ago

Looks like wp-pull-production-db gets only 1024MB memory, even if memory limit would bet set higher from php.ini

DEVELOPMENT [@alvarpet:~] $ wp-pull-production-db
Saving backup of current development database in /data/db/pre-production-pull-backup.sql...
Success: Exported to '/data/db/pre-production-pull-backup-20210528-151315.sql'.
Define new and old siteurl for later search-replacing...
alvarpet@alvarpet.de.seravo.com's password: 
==> This is a normal WordPress single install.
==> Production site URL: https://alvarpet.com
==> Development site URL: https://alvarpet.local
Is the information above correct? (y/n): y
Pulling database from production with 'wp db export'...
alvarpet@alvarpet.de.seravo.com's password: 
PHP Fatal error:  Allowed memory size of 1073741824 bytes exhausted (tried to allocate 534773792 bytes) in phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/utils.php on line 546
Success: Imported from 'STDIN'.
Search-replacing https://alvarpet.com with https://alvarpet.local...
Success: Made 0 replacements.
Flushing cache to ensure new database contents is used on site
Success: The cache was flushed.
DEVELOPMENT [@alvarpet:~] $ php -i | grep "memory_limit"
memory_limit => 2048M => 2048M