Skip to main content
11
results
Andrew Fletcher
The issue of over 300 simultaneous database connections in the context of AWS and Drupal can have several potential causes. Here are some common factors to consider: Server Configuration Check your server configuration to ensure it can handle the expected number of simultaneous connections. This includes parameters like max_connections in your database server configuration. Traffic or Load Spike A sudden increase in traffic or load on your Drupal site can lead to more simultaneous database...
Andrew Fletcher
Working in an AWS ec2 environment, my goal is to access the server via...
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
Currently, I have a situation where I have two repositories.  The first is where I've held the code since the beginning.  The second has come on board recently and is the client repo.  However, rather than shut the original down, I want to keep both running with the same code.  How do I synchronise them so that they contain the same thing? Configure a remote that points to the upstream repository in Git to sync changes you make in a fork with the original repository....
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
Having Drupal Solr Search APi running, I thought adding synonyms to the mix...
Andrew Fletcher
Wanting to create a new repository on GitHub, add in a few of the available...
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...