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
•
This page will be a progressive outline of moving those regular run scripts that really need to be automated. Or triggered by a keyword.
These scripts are rsync commands
The initial scripts
production environment
sudo rsync -aur staging/{project}/config drupal
cd drupal
sudo chown -R www-data:www-data config
cd ..
sudo rsync -aur staging/{project}/core drupal
cd drupal
sudo chown -R www-data:www-data core
cd ..
sudo rsync -aur staging/{project}/modules drupal
cd drupal
sudo chown...
Andrew Fletcher
•
Tailwind CSS is a highly customisable framework that delivers developers the...
Andrew Fletcher
•
Currently, I have a situation where I have two repositories. The first is...
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 response:
fatal: The current branch main has no upstream branch.
To push the current branch and set the remote as upstream, use
git push --set-upstream origin main
Quick solution, instead run the command
git push origin mainAnd the response will push what you were attempting to do
Enumerating objects: 34, done.
Counting objects: 100% (34/34), done.
Delta compression using up to 8 threads
Compressing objects: 100% (19/19),...
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...
Andrew Fletcher
•
Wanting to create a new repository on GitHub, add in a few of the available...
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...