Fix Composer Process Timeout Issues

Recently I started contributing to an Open Source WordPress plugin and unfortunately I kept hitting a wall with the process timeout caused when installing Composer dependencies.

After some research, I found several ways to by-pass this timeout, one of which was decided to implement in the package.


The recommended way of disabling the Composer timeout is on each script execution, using the builtin method provided by Composer: Composer\Config::disableProcessTimeout. Doing so keeps the timeout setting specific to tasks and does not pass this setting to other scripts or processes.

scripts: {
  "pre-install-cmd": [

Other Methods

The following is a set of other methods which also disable the timeout, but can be destructive when the timeout serves a distinct purpose.

Set Globally

The quickest (and probably most distructive) way to disable the timeout is by setting the var on your system.


Set for a Package

Optionally you can set the timeout within the package config:

config: {
  "process-timeout": 600

Set for a Command

Another way would be to set the timeout for each individual command.

COMPOSER_PROCESS_TIMEOUT=600; composer install

The first two are still a bit overbearing, while the third would only apply to that specific command, and that can be useful in many circumstances.

Personally, I use the recommended method or the per-command method when I need a quick process timeout removal.


Escape to the Ocean

As the water briskly bumps against the hull, I find myself breathing in the crisp, salty air from the sea. Gazing just above the horizon, there is a faint glimpse of the rock softly peaking in the daylight.

A journey away from land to find peace.

As we are sheltered in during this pandemic, time and again I am drawn to my wanderlust, fortunate to have visited so many places which now seem out of reach.

Let us cherish these fleeting moments. ❣️


Know Your Value

One day my grandfather gave me an old watch, explaining to me that his father carried this watch during his time serving in World War I.

Upon giving me this watch my grandfather asked me to take it to the local pawn shop and jewelers to get it appraised. Not quite sure the reason for the ask, I reluctantly agreed. When I returned with the watch, I informed my grandfather the pawn shop offered $150 and the jeweler offered $325.

“Now take it to the museum, and ask what they would give for it”, my grandfather said. So I visited the museum and, too my surprise, they offered me $750,000. 😳

After returning to my grandfather and explaining the large offer from the museum, he told me “There will be many people in your life, surround yourself with people that recognize your value.”

This fictional story was an adaptation of an old parable about a dying father, his son and an old family watch. It really touched me and forced me to understand and recognize those around me which do not acknowledge or realize my value.

We will often times find ourselves challenged with difficult decisions, especially when it comes to value recognition. Coming in the form of family, friends, colleagues and even your employers; lack of value recognition leads to negativity and ultimately unhappiness.

Be valued. Be happy. 😎


Hello World. 👋🏻🌎

Hello, again and again and again, World. 👋🏻

Over the course of my hosting websites I have transitioned sites offline and back online several times, all while auditing the site content to see if I wanted to transition it as well.

Now, in the midst of a Global Pandemic, I am once again performing this transition. While these two are completely unrelated, it is definitely something which has been on my todo list for quite some time.

Oooh, something new…

So, what’s new?

Previously this site was hosted as a WordPress single installation Pantheon’s platform. While I still love Pantheon, I have been looking for a solution which could incorporate a WordPress Network of sites, so that management of all sites fall under one roof.

Now, I know what you may be thinking… a Network? Really?

While there are many reasons to use a WordPress Network, often times creating a network in which each site has its own domain is not the best solution for the problem. That being said, if done right a WordPress Network of sites can perform just a well as any single site installation.

Emphasis on “if done right”.

Since Pantheon does not offer WordPress Networks out of the box (you have to get approved by Pantheon and be on a specific Plan), I choose to move off Pantheon and give SpinupWP a try.

Now, after a few months of hosting on SpinupWP, I have to say I am quite pleased with the simplicity of the platform. The ease of deploys and updates, the barely-opinionated structure of repos and the developer centric focus of work is all quite pleasing.

Unlike other platforms, one of the biggest benefits of using SpinupWP is cost (which was a huge decision driver). Currently we are paying about $50 a month to host eight sites; whereas on Pantheon that would cost roughly $280. Sure, there is a little more legwork involved, but I am a DIY type of person already, so I don’t mind getting my hands dirty.

TBH, I feel this will be one of the last transitions I will ever make with my sites (may switch hosts in the future, because you never know 🤷🏻‍♂️), but will ultimately keep the WordPress Network structure to keep all our sites under one ☂️.

Cheers. 🍻