ScottPhillips

#301 Redirects for .htaccess

#Redirect a single page:
Redirect 301 /pagename.php http://www.domain.com/pagename.html

#Redirect an entire site:
Redirect 301 / http://www.domain.com/

#Redirect an entire site to a sub folder
Redirect 301 / http://www.domain.com/subfolder/

DavidWittman

backend default {
  .host = "127.0.0.1";
  .port = "8080";
}
backend master {
  .host = "10.x.x.x";
  .port = "80";
}
sub vcl_recv {
  # Any uploads or restarts should go to the master backend

fideloper

<?php  if ( ! defined('BASEPATH')) exit('No direct script access allowed');

//Create a new config file

/*
|--------------------------------------------------------------------------
| Number of databases in use
|--------------------------------------------------------------------------
|
| Using a Master and Slave. The Slave doubles as a read-only database.

petecoop

<?php
function compareImages($imagePathA, $imagePathB, $accuracy){
  //load base image
  $bim = imagecreatefromjpeg($imagePathA);
  //create comparison points
  $bimX = imagesx($bim);
  $bimY = imagesy($bim);
  $pointsX = $accuracy*5;
  $pointsY = $accuracy*5;
  $sizeX = round($bimX/$pointsX);

aderowbotham

How to purge ('ban') an entire domain in Varnish Cache 3

#####EDIT: NB Ban is technically different from Purge. Banned objects remain in memory but banning is faster than purging. Read the Varnish 3 documentation here and here.

Purge may be a more appropriate action for your use-case; although the examples in the gist below work, it's not necessarily the best way of doing this.

---

juampynr

dependencies[] = ctools

; Views Handlers
files[] = views/mymodule_handler_handlername.inc

fabarea

<?php

use Behat\Behat\Context\ClosuredContextInterface,
	Behat\Behat\Context\TranslatedContextInterface,
	Behat\Behat\Context\BehatContext,
	Behat\Behat\Exception\PendingException;
use Behat\Gherkin\Node\PyStringNode,
	Behat\Gherkin\Node\TableNode;

use Behat\MinkExtension\Context\MinkContext;

kevin-smets

Default

Powerlevel10k

swichers

In a module file:

This will enable an additional view mode for use on the specified entity type(s). Many examples will show the custom settings here being set to TRUE. If TRUE is used then that view mode is added to all entities of the specified type regardless of if it should be on the bundle or not.

/**
 * Implements hook_entity_info_alter().
 */
function HOOK_entity_info_alter(&$entity_info) {

jemond

<?php
/**
 * @file
 * Custom Drush integration.
 */

/**
 * Implements hook_drush_command().
 *
 * @return