Drush 10

Drush: Setting up and Leveraging Site Aliases

If you haven't yet set up site aliases for Drush, what are you waiting for?!?--Life is so much easier once your localhost can start communicating with your remote: bring site files and databases straight from production to local without logging into your CPanel or PHPMyAdmin; clear site cache on Production without logging into the site and navigating the admin UI. It can be tricky to set up, but once you have, you'll wonder how you ever developed without site aliases.

Background: Why Site Aliases Rock

My main client is hosted on Acquia; despite the tendency to be both pedantic and overly optimistic in regards to all things Drupal, Acquia, as a company, can be extremely considerate to the developers on its platform. One of the perks of being with Acquia is having out-of-the-box support for Drush Site Aliases.

Web Developer Workflow: More Useful Linux Bash Aliases

More Bash Alias fun. This time we'll look at Git, Drush and a few others.

Intro

This is a followup to another recent post discussing bash aliases meant to make your web-developer life easier. If this is your first Tango with Bash Aliases, head to that post for an intro to working with aliases. Otherwise--the list goes on!

Drupal 9 Upgrade: Start to Finish

Good news: after all the sweat and blood of getting our site ready, the upgrade took all of 30 minutes. This really may be the easiest Drupal upgrade in a decade. It's still not for the faint of heart. Here's a quick recap on the steps necessary to do this upgrade. I'll be sure to link back to my previous articles so you can see the work and challenges involved with each step in detail.

Drupal 9 Up Front

Compared to all the work that went into prepping the site, the actual upgrade is a walk in the park. I'll be sure to cover the actual upgrade process in Step 5 of this article; I'd like to do a quick recap on the entire process, though--so, if you've already read my earlier Drupal 9 Upgrade posts, feel free to skip to Step 5. Otherwise, let's reconnect with what the basic steps are for a D8 to D9 upgrade.

Drupal 9 Upgrade: Composer and Drupal's Module Directory

It seems like a no-brainer to me, but I must have missed something. Why Drush, Drupal's admin UI and Composer would install modules into different directories by default is beyond me.

Default Module Directory

Where are modules really supposed to go, anyways? Here's what Drupal.org has to say:

Drupal 9 Upgrade: Issues with Composer

The upgrade from Drupal 8 to 9 has been hailed by Drupal.org as the easiest upgrade in a decade. The first steps in the upgrade process look to be getting your testing environment in order... for me, that means working through a couple of nasty headaches with Composer (self inflicted... of course).

It's been a long couple of weeks...

... long...