developer resources
Codebales holds an ever growing number of solutions to problems that we have experienced in our day to day code writing
Selected filter
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
•
Working in Laravel, I needed to loop through an array and know whether the...
Andrew Fletcher
•
Setting up the mail configuration in October CMS is a quick progress. Depending on which mail method you use there are up to eight fields to complete:
Sender name;
Sender email;
Mail method: (PHP mail, Sendmail, SMTP, etc...). I elected to go with SMTP;
SMTP address - such as smtp.your-domain.com or mail.your-domain.com;
SMTP port - 587;
SMTP encryption protocol - TLS or SSL;
Authorization required - boolean response;
Username - email account; and
Password -...
Andrew Fletcher
•
The purple warning notification of annoyance recently came my way! I...
Andrew Fletcher
•
Common commands
Themes and plugins have similar command lines. So rather...
Andrew Fletcher
•
At times while developing in October CMS, you will perform a step that kills the...
Andrew Fletcher
•
Using October CMS to migrate your site and update the tables with the plugins...
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...