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
•
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...
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 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
•
Installing Varnish to increase the speed of the page load.
Install varnish using...
Andrew Fletcher
•
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
•
To add ejabberd and run MYSQL to the server I needed to update the server...
Andrew Fletcher
•
Installing Laravel on an Apache server was going to be a no fuss process said no...
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...