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
•
Setting up the admin password.
Process:
1. Edit jetty.xml
To begin you are going to edit the file “server/etc/jetty.xml”. However, if you aren't sure of the location of jetty.xml, run the command
find / -name jetty.xml -type fFor me, the output was
/opt/solr-8.11.1/server/etc/jetty.xmlEdit the file jetty.xml, by adding it before the Configure tag ends
<Callname="addBean">
<Arg>
<New class="org.eclipse.jetty.security.HashLoginService">
<Set...
Andrew Fletcher
•
In this article I'll walk through the steps I went through to install Solr on...
Andrew Fletcher
•
Looking to install Solr on your server? Not sure if it worth the...
Andrew Fletcher
•
Currently, I have a situation where I have two repositories. The first is...
Andrew Fletcher
•
ERROR Error: Uncaught (in promise): TypeError: undefined is not an object...
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
•
Having Drupal Solr Search APi running, I thought adding synonyms to the mix...
Andrew Fletcher
•
Wanting to create a new repository on GitHub, add in a few of the available...
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...