temperatio

The perfect Varnish configuration for Joomla, WordPress & other CMS based websites

IMPORTANT: Read this before implementing one of the configuration files below (for either Varnish 3.x or 4.x+).

USE: Replace the contents of the main Varnish configuration file located in /etc/varnish/default.vcl (root server access required - obviously) with the contents of the configuration you'll use (depending on your Varnish version) from the 2 examples provided below.

IMPORTANT: The following setup assumes a 180 sec (3 minute) cache time for cacheable content that does not have the correct cache-control HTTP headers. You can safely increase this to 300 sec (or more) for less busier sites or drop it to 60 sec or even 30 sec for high traffic sites.

This configuration requires an HTTP Header and a user cookie to identify if a user is logged in a site, in order to bypass caching overall (see how it's done for Joomla & WordPress). If your CMS provides a way to add these two requirements, then you can use this configurati

temperatio

<?php
// Clear items that are older than a 7 days (i.e. keep only the most recent 7 days in the log)
add_filter( "simple_history/db_purge_days_interval", function( $days ) {

	$days = 7;

	return $days;

} );

temperatio

const { src, dest, watch } = require('gulp');
const sass = require('gulp-sass');
const minifyCSS = require('gulp-csso');
const babel = require('gulp-babel');
const concat = require('gulp-concat');
const browserSync = require('browser-sync').create();

function css() {
    return src('./sass/*.scss', { sourcemaps: true })
        .pipe(sass())

temperatio

<?php // only copy this if needed

/**
 * Changes excerpts displayed on restricted membership content to use 120 words
 * instead of WordPress default.
 *
 * @since 1.6.0 
 * @param string $content HTML content displayed for the post 
 * @param bool $restricted Whether the content is restricted 
 * @param string $message The restriction message applied, could be empty string 

temperatio

registerBlockType( 'loomo/yoshi-cookies', {
	category: 'mario-blocks', // Block category

temperatio

Paprika doesn't have their API documented, so this is me reverse-engineering it from an Android device

Live Demo

https://knowing-grain.glitch.me/

Sync

HTTP BASIC auth (emoji shrug), and send a GET to:

temperatio

SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';

CREATE SCHEMA IF NOT EXISTS `survey_001_models_from_tables` DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci ;
USE `survey_001_models_from_tables` ;

-- -----------------------------------------------------
-- Table `survey_001_models_from_tables`.`organizations`
-- -----------------------------------------------------

temperatio

#!/bin/bash
#############################################################
# Script para convertir un repositorio de git en compartido #
#############################################################
if [ "$(id -u)" != "0" ]; then
	echo "Este script hay que ejecutarlo con permisos de root"
	exit 1
fi
if [ "$#" -ne 1 ]; then
	echo "Sólo puede haber un parametro"

temperatio

#!/bin/sh

# Create a db dump and upload it to another server
#
BACK_SERVER='xxx.xxx.xxx.xxx'
BACK_SERVER_PORT='22'
BACK_SERVER_USER='user'


# store current date

temperatio

#!/bin/sh

# Create a db dump and upload it to another server
#
BACK_SERVER='xxx.xxx.xxx.xxx'
BACK_SERVER_PORT='22'
BACK_SERVER_USER='user'

# Database credentials
DB_NAME='database'