Skip to main content
11
results
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
The cache system in Drupal 9 delivers the API with the elements required for...
Andrew Fletcher
Installing Varnish to increase the speed of the page load. Install varnish using...
Andrew Fletcher
Clear DNS Cache The DNS (Domain Name Service) cache on your Mac helps browsers locate and connect to web addresses quickly. If your browser Safari or Chrome still fails to load websites, this can be the result of an obsolete DNS cache may be causing the issue. In this instance you want to focus clearing the cache.  Using Terminal or iTerm2 enter the following command: sudo killall -HUP mDNSResponder 
Andrew Fletcher
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
The purple warning notification of annoyance recently came my way!  I...
Andrew Fletcher
iOS localization on the fly If you have added languages to your app......
Andrew Fletcher
Localization is the process of showing other languages in your app and is...
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...