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
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 similar to a Bitbucket profile.  Logged in to your GitHub account, click your profile icon, located (at the time of this writing) on the top right corner.  Select Settings Click SSH and GPG Keys Click Add New SHH KeyA new page will open  requiring Title Key Type a title that represents the project you are working on. Open your terminal application and enter the command ls -al ~/.sshThe period...
Andrew Fletcher
Installing Varnish to increase the speed of the page load. Install varnish using...
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...