Skip to main content
11
results
Andrew Fletcher
Updating NPM packages using npm update and I'm seeing the following response npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@fortawesome%2fpro-light-svg-icons - Not found npm ERR! 404 npm ERR! 404 '@fortawesome/pro-light-svg-icons@^5.11.2' is not in this registry. npm ERR! 404 @fortawesome:registry=https://npm.fontawesome.com/ npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url. npm ERR! A complete log of this run...
Andrew Fletcher
Looking to install Solr on your server?  Not sure if it worth the...
Andrew Fletcher
Currently, I have a situation where I have two repositories.  The first is...
Andrew Fletcher
When attempting to do a git push, are you getting the following...
Andrew Fletcher
In this woalk through I am going to use GitHub.  However, the steps are...
Andrew Fletcher
Installing Varnish to increase the speed of the page load. Install varnish using the command below yum install varnishYour response should look something like Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.realcompute.io * epel: epel.mirror.digitalpacific.com.au * extras: mirror.realcompute.io * updates: centos.mirror.digitalpacific.com.au Resolving Dependencies --> Running transaction check ---> Package varnish.x86_64 0:4.0.5-3.el7 will be...
Andrew Fletcher
If you are using theme_get_settings, such as: $value =...
Andrew Fletcher
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
To add ejabberd and run MYSQL to the server I needed to update the server...
Andrew Fletcher
Installing Laravel on an Apache server was going to be a no fuss process said no...
Andrew Fletcher
As a process I apply patches locally first, then using git upload the update(s) to a development site on the server.  Once the testing has been completed, the final step to apply the patch to the production site.   Using Terminal or your preferred shell program, navigate to the correct directory.  Then run this command using the name of the patch file (example.patch): patch < example.patchHowever, if you are patching Drupal core then remember to patch from the root directory...