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
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
I had been running a few Centos 6 servers just past their EOL (30th November...
Andrew Fletcher
Core Data - customising our data model When you are using Core Data, and let's say that you have a requirement to have an attribute where the options available should be a defined list.  Such as "Not Started", "Pending", "In Development" and "Completed".  How do you create this as an option in Core Data?   Thinking out loud, the practical solution would be to use an enum.  But how do you use a enum in this instance?  As you might have noticed, unfortunately, it...
Andrew Fletcher
I need to set the default php-version of a subscription to php7.3.  The...
Andrew Fletcher
(104)Connection reset by peer: mod_fcgid: error reading data from FastCGI...
Andrew Fletcher
To add ejabberd and run MYSQL to the server I needed to update the server...
Andrew Fletcher
Images For some time, when looking for images online for your app or site I have...
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...