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
•
Working on a decoupled React / Drupal 9 site.
Aim: Adjust the output of curated...
Andrew Fletcher
•
How to make React calls on a Drupal 9 backend site using the search...
Andrew Fletcher
•
When attempting to do a git push, are you getting the following...
Andrew Fletcher
•
This code is from Drupal 9 back-end for a React front-end via REST API.
Working...
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
•
Have you noticed through your Google account that there are items being indexed...
Andrew Fletcher
•
I’m recently doing an IoT project. I wanted to investigate the network...
Andrew Fletcher
•
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
•
Load testing verifies the system performance under the expected peak load....
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...