Disable Xdebug running Composer on Trellis

When you use Trellis for local WordPress development, Xdebug is installed for debugging. This can be very useful. But when you run composer to update plugins, WordPress and so on and use Xdebug composer will become very slow. And you will get this warning

You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug

Chris Loftus wrote about it . He explained how to Disable Xdebug running Composer.  He offered a solution to keep on using Xdebug but not while running cli stuff. A solution for setups with Ubuntu and PHP 7. And As we know that is what Trellis uses. So an awesome solution how to disable Xdebug running Composer on Trellis! The solution is to run the following command:

sudo phpdismod -s cli xdebug

This will disable Xdebug for CLI purposes. To quote Chris again:

The -s flag tells it to disable Xdebug for the CLI SAPI (/etc/php/7.0/cli) and not FPM.

And that is what we are looking for. I still want to be able to use Xdebug, but I do want composer to run smoothly and as fast as possible on my local Trellis LEMP server.

Once you have run that command you will no longer get the warning. Composer will be considerably faster from that moment on.

WordPress – Simply Good for Business

In this blog post I am going to show you why WordPress is such a great platform for content creation online. WordPress is simply good for business for many reasons and though some may always be partially subjective or just subjective please just bear with me.

Twenty Five Percent of the Web Can’t Be Wrong

25.5% of the web

WordPress powers 25.5% of the web and 30.3% of top 1000 sites. So that means a lot of people like using it. Also that a lot of companies and professionals do too. Companies like Sony, Time, Samsung, Linked and celebrities like Jay Z, Snoop Dog and Malala Yousafzai use WordPress. Here is a list of Fortune 500 companies using WordPress. And the reason they are using it? WordPress is simply good for business they found out.

Now the reasons you should go for WordPress one by one:

User Experience

user experience


As iThemes mentioned in their blog article, “it’s probably the easiest and most powerful blogging and website content management system (or CMS) in existence today”. Usage is often a personal experience and mine is of course too. But I have worked with other content management systems in the past. CMSs like Joomla!, Drupal, Typo3, Ghost and others. And WordPress’ Dashboard is just very intuitive and easy to learn. The Customizer to adjust the looks of your site and widgets are just amazing. Content creation using posts and pages is just not difficult at all. Also, there is plenty of help out there, either paid or for free.

Here a list of WordPress features that make it very user friendly:

  • widgets – easy way of drag and dropping content blocks into place
  • customizer – easy way to manage all elements of your theme from one location with live preview
  • posts – built for blogging with easy to set up hierarchy
  • wysiwyg – beautiful content editor with full screen zen mode
  • mobile friendly – WordPress Dashboard is fully responsive


huge ecosystem

The ecosystem of plugins to extend the functionality and themes to give your site the needed look is just wonderful. This is really important. So many free and commercial themes and plugins out there. It is unbelievable. There is no other rival CMS that offers this many themes and plugins to choose from. None. Just look at what a company like Themeforest offers in the WordPress section alone. It is truly phenomenal.

When I talk about the ecosystem I am including the community mind you. The WordPress online presence is truly magnificent. So many online resources and fora to read up on WordPress and to get help. The organization behind Joomla! has had quite a few issues the last couple of years. One of the reasons I left that CMS. The organization and people behind WordPress with Automattic and benevolent dictator Matt has thrived like no other. So in brief:

  • enormous and friendly online community
  • large online grid of documentation and tutorials
  • themes – huge amount of free and commercial themes
  • plugins – over 42.ooo plugins to extend your setup


open source - free

WordPress is 100% Open Source, baby! Nobody owns WordPress nor its themes nor its plugins. Everyone can use them for free and fork them to make them better. All is free for use as long as you follow the basic GPL licensing rules. Open Source makes sure nothings gets stuck behind licensing walls and that all keeps on growing. Beautiful!

Reasons for going for WordPress in Brief

So to summarize it all, it all comes down to is:

  • usability- very user friendly and easy to use
  • licensing – is it closed source or open source / what do extensions and or themes cost
  • eco system – large enough to sustain users and to grow and with solid enough leadership

And so far the answer has been yes to all three. Usability is great, licensing is open source and there is an amazing ecosystem out there waiting to be embraced. Plenty of reasons explaining why WordPress is simply good for business

Download failed. Failed to write request to temporary file

Just had an issue with updating all plugins on a Dreamhost VPS. None would update. All plugins showed this error when I tried to update them:

Download failed. Failed to write request to temporary file.

A bad start of my morning. Fortunately Dreamhost has great live chat any time of the day and they confirmed what I found out Googling. Apparently the /tmp folder had reached its 128MB max (Dreamhost set limitation. This was due to too many left over files in the folder. This caused issues and that is why the server failed to write request to temporary file, meaning the /tmp directory.

Cause TMP folder Issues & Solutions

The pile up had probably been caused by plugins or PHP misbehaving. Dreamhost staff member Vince emptied the folder for me. He told me for future reference that I could also restart the VPS if I ran into this issue again in the future. Below I will show why that is for my situation. If you do have full access to the server you can just manually empty it yourself of course. No need to reboot in that case.

Ubuntu and /tmp

Dreamhost VPSs run Ubuntu 12.0.4 LTS. I found a good SO explanation how the emptying works for Ubuntu versions before 14.0.4:

The cleaning of /tmp is done by the upstart script /etc/init/mounted-tmp.conf. The script is run by upstart everytime /tmp is mounted. Practically that means at every boot.

The script does roughly the following: if a file in /tmp is older than $TMPTIME days it will be deleted.

The default value of $TMPTIME is 0, which means every file and directory in /tmp gets deleted. $TMPTIME is an environment variable defined in /etc/default/rcS.

So as Vince said rebooting does do the job. In 14.0.4 up it is taken care of by tmpreaper.

Locate tmp directory

If you would like to find out what temporary directory is you can use the following PHP function:


See PHP manual details here. In case the location it uses does not work you can set another location adding something like the following to wp-cponfig.php:

define('WP_TEMP_DIR', dirname(__FILE__) . '/wp-content/temp/');

Found information on this in this WordPress Stack Exchange thread.