Yesterday morning I wrote an article on installing Lando into Ubuntu WSL 2, using the latest and greatest Docker Desktop (release 3.2.x).
If you are one of the 3 anonymous cats and 1 rottweiler dog that follows this blog, you probably figured out that I’d be a matter of when, not if I would attempt the same on Alpine.
I’m happy to report that it looks like the approach detailed in this story was successful. Earlier today I had tried to install Lando from a
In the recent weeks I’ve been running into issues when cloning from remote Git repositories. Not just on Github.com, but elsewhere as well. Some repos would clone, others would fail with obscure messages. For a while no amount of Googling would lead me to a favorable result. Updating all of packages inside the WSL distro? Done. Updating OpenSSL and
ca-certificate packages? You got it. Still the same issues.
There’s two resources that ended up solving the issue:
The first one is in Japanese, which I definitely don’t understand. But command line…
My main driver in WSL2 is usually Alpine, but I’ve initially encountered some issues with installing Lando there. Alpine is not for the weak! Instead I am going to use Ubuntu (18.04) in WSL2, and install Lando there.
Or: How to remove endless number of sessions
Note: if you want to know how to create your own SSH keys, visit Github to read Generating a new SSH key and adding it to the ssh-agent, and Testing your SSH connection.
Which means my current
.bashrc is adding my SSH private keys to my SSH agent. It works well, here is my current
Today, I began my day by looking at this monstrosity of a Docker image for Apache Solr:
The image is fresh (from this month), and for all it’s worth it is as well constructed as it can be — it is after all, the official image from the World Wide Web Supremos over at the Apache Foundation.
But Dear Lord, isn’t it unabashedly large sitting at 267.24 MB! That’s just the first thought of the day. The image uses a debian/ubuntu base as betrayed by the
apt-get usage in the
Dockerfile commands, and that could be part of the…
It’s been a few years since I’ve touched a Varnish VCL. VCL is the Varnish Configuration Language. 2010 was the first time that I used Varnish while supporting a high traffic Drupal 6.x site for some media company headquartered in New York City.
Today I was tweaking and optimizing my NGINX Docker configurations when I ran into a relatively recent story about Drupal 8 performance. The breadcrumbs went something like this:
WSODs are dreaded but also legendary within the PHP and Drupal communities as they happen when your PHP process encounters an error that it cannot recover from, therefore presenting you with a White Screen of Death.
Luckily, even with the WSOD, after the install finished Drupal logged me in as the new admin user I created, so I was able to access the site’s…
I remember when I landed my first job in continental United States, having moved from insular Puerto Rico to New York after the 2007–2009 Great Recession.
It was at the tony New York City headquarters of Time Out New York, back when Time Out was a separate entity from Time Out London. They were switching from a Java backend to a PHP/Drupal-based stack, and that’s where me and two other new Drupal developers came in. The sole remaining Java developer in the company (who dabbled in PHP), had requisitioned 3 new Windows 7 machines for us and installed XAMPP on…
It’s that time of the year (or decade) where I’m again shopping for a new job, stepping outside of the enterprise bubble that I’ve lived for the last 3+ years. Of the the dozens of interviews I have conducted so far I yet have to find an organization that is using Docker, in the year 2020.
All of the Drupal shops I’ve talked to so far are still using Acquia Dev Desktop, an 8 year old or so technology. And why blame them? It’s the lowest entry barrier to Drupal.
So I’d thought I’d take Acquia Dev Desktop for a…
After having successfully integrated the Spotify Web Playback SDK (at least initially) with the help of castLabs Electron distribution, I find myself peering again into the void of software development errors.
Using the same Quick Start example I used for my previous stories, I am able to get a
Ready with Device ID connection message to the SDK. Nothing but Fair Winds and Blue Skies from there on, right?
Not so much. After manually switching the playback device from my main Spotify application to the Quick Start example, the audio starts playing in the example application (castLabs Electron), but the…