Skip to main content
11
results
Andrew Fletcher
Visual Studio Code (VS Code) allows you to manage extensions using the VS Code Command Line Interface (CLI) called code. With the code CLI, you can install, list, uninstall, and manage extensions from the command line.   To check you have the code prompt running, run code --versionResponse you're looking for is 1.83.0 d3a019177ff8833cf320e334265dfea540098a3a arm64If not, to install, in VS Code press command + shift + p to open the command palette, then type "install code", click Shell...
Andrew Fletcher
A summary of Node package commands Short cut commands npm install...
Andrew Fletcher
Setting up the admin password.   Process: 1. Edit jetty.xml To begin you...
Andrew Fletcher
In this article I'll walk through the steps I went through to install Solr on...
Andrew Fletcher
Looking to install Solr on your server?  Not sure if it worth the...
Andrew Fletcher
phpcs issue in Visual Studio Code, I'm receiving this warning in VS Code: phpcs: Unable to locate phpcs. Please add phpcs to your global path or use composer decency manager to install it in your project locally.  How to fix You can install phpcs by using composer global command: composer global require squizlabs/php_codesnifferThen in VS Code, go to  Click Code -> Preferences -> Settings Select User Settings and locate 'PHP CodeSniffer', or in the Search settings enter...
Andrew Fletcher
Having Drupal Solr Search APi running, I thought adding synonyms to the mix...
Andrew Fletcher
Setting up a new project in Docker and VS Code. Using Terminal, go to your...
Andrew Fletcher
Step 1: Install Homebrew Homebrew is the missing package manager for macOS. As...
Andrew Fletcher
Working on a new CentOS 7 server, Node wasn't installed.  You can...
Andrew Fletcher
I started out with a simple task... install Tailwindcss.  What unfolded is something that many of us have experienced time and time again. For anyone that has completed this task before knows that through shell the command is # Using npm npm install tailwindcssHowever, before doing so I wanted to check the version of node on the server and in Plesk.  The shell command node -v was showing v7.10.1 whereas in Plesk v10.16.0.  Not great being a few versions behind....