WordPress in production

Share this post on:

WordPress should not expose warnings and other verbose data in production. On earth, so many configurations such as multiple revisions are not used in such a depth in most cases. So many of obsessive configurations may slow WordPress down.

We change configuration of WordPress only from wp-config.php so we can have a backup of original configuration and this file can act simply as a restore point to discard all changes in case of any trouble.

Don’t change core files. If there is a critical update, contribute to the WordPress project’s repository. If you have some common optional configurations, add it to a plugin. Respect the project modularity.

define('FS_METHOD', 'direct');
define( 'WP_POST_REVISIONS', 2 );
define( 'EMPTY_TRASH_DAYS',  2 );
define( 'AUTOSAVE_INTERVAL', 180 ); // 3 mins
define( 'WP_ALLOW_REPAIR', true );
define( 'WP_MEMORY_LIMIT', '512M' );
define( 'WP_MAX_MEMORY_LIMIT', '1024M' );

ini_set('error_reporting', E_ALL );
define('WP_DEBUG', false);
define('WP_DEBUG_DISPLAY', false);

File permissions

sudo chown -R www-data:www-data ../wp
sudo find . -type d -exec chmod 755 {} \;
sudo find . -type f -exec chmod 644 {} \;
Share this post on:

Author: tayyebi

Tayyebi works in the role of Director at Gordarg where he is the founder. He is passionate about people, technology, and arts. Mohammad believes in communications, each of us has the power to empower their people with knowledge. He can be seen writing codes, playing music, biking, and reading.

View all posts by tayyebi >