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
•
Goal: Restrict content access through username and password entry on an Nginx server.
1: Apache Utilities Package
First, update your server’s package index:
sudo apt updateCheck if the utilities package exists in your environment by executing the command
dpkg --get-selections | grep apacheResponse:
apache2-utils install
libapache-pom-java installSo it exists. But what do you do if it doesn't exist?
How come I need to install apache-utils? To restrict access you will be using...
Andrew Fletcher
•
Setting up the admin password.
Process:
1. Edit jetty.xml
To begin you...
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
•
Goal: Restrict content access through username and password entry.
1: Apache...
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
•
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...