derekconjar

<?php

/**
 * All custom functions should be defined in this class
 * and tied to WP hooks/filters w/in the constructor method
 */
class Custom_Functions {

  // Custom metaboxes and fields configuration

mwpastore

README

This gist assumes you are migrating an existing site for www.example.com — ideally WordPress — to a new server — ideally Ubuntu Server 16.04 LTS — and wish to enable HTTP/2 (backwards compatibile with HTTP/1.1) with always-on HTTPS, caching, compression, and more. Although these instructions are geared towards WordPress, they should be trivially extensible to other PHP frameworks, other FastCGI backends, and even non-FastCGI backends (using proxy in lieu of fastcgi in the terminal Caddyfile stanza).

Quickstart: Use your own naked and canonical domain names instead of example.com and www.example.com and customize the Caddyfile and VCL provided in this gist to your preferences!

These instructions target Varnish Cache 4.1, PHP-FPM 7.0, and Caddy 0.10. (I'm using MariaDB 10.1 as well, but that's not relevant to this guide.)

redoPop

# This is a template .gitignore file for git-managed WordPress projects.
#
# Fact: you don't want WordPress core files, or your server-specific
# configuration files etc., in your project's repository. You just don't.
#
# Solution: stick this file up your repository root (which it assumes is
# also the WordPress root directory) and add exceptions for any plugins,
# themes, and other directories that should be under version control.
#
# See the comments below for more info on how to add exceptions for your

publicarray

// https://developers.cloudflare.com/workers/about/ 
// https://tutorial.cloudflareworkers.com
//
// A Service Worker which adds Security Headers.
// Checks:
//     https://securityheaders.io/
//     https://observatory.mozilla.org/
//     https://csp-evaluator.withgoogle.com/
//     https://hstspreload.org/
//     https://www.ssllabs.com/ssltest/

n-ts

/*
--------------------------------------------------------
Please note that this grouping is just for example...
You can rearrange POPs, remove or add dacaneters according to your needs.
--------------------------------------------------------

First, we have to get all Cloudflare POP codes (three letter airport codes) from https://www.cloudflarestatus.com/

North America is routed to Chigaco datacenter;
Europe, Africa and Middle East is routed to Amsterdam datacenter;

wincent

#!/bin/bash

#
# https://support.1password.com/command-line-getting-started/
#
# Full docs: https://support.1password.com/command-line/
#
# gpg --receive-keys 3FEF9748469ADBE15DA7CA80AC2D62742012EA22
# gpg --verify op.sig op
#

qsun

<?php

function indexed($url) {
    $url = 'http://webcache.googleusercontent.com/search?q=cache:' . urlencode($url);
    
    $ch = curl_init($url);
    curl_setopt($ch, CURLOPT_FOLLOWLOCATION, false);
    curl_setopt($ch, CURLOPT_NOBODY, true);
    curl_setopt($ch, CURLOPT_USERAGENT, 'Chrome 10');
    

carlosleopoldo

DELETE FROM wp_usermeta
WHERE NOT EXISTS (
  SELECT * FROM wp_users
	WHERE wp_usermeta.user_id = wp_users.ID
)

brenes

// This script is based on https://ithoughthecamewithyou.com/post/automate-google-pagespeed-insights-with-apps-script

// STEP 0: Create a spreadsheet document on Google Drive, go to the code editor 
//         (in spanish "Editor de la secuencia de comandos").
//         Then paste this code and modify it.


// STEP 1: Insert your pagespeed API KEY
var pageSpeedApiKey = '';
// STEP 2: Insert the monitored URL

jakebellacera

// The script below will ensure that gclid parameters are associated with
// contacts in HubSpot.
//
// A few things are required before this script will work:
// 
// * You will need to have the HubSpot tracking code installed on the page. A
//   few modifications will be required if you don't have the tracking code
//   installed. Additionally, you will lose out on the built-in cross-domain
//   features that the hubspot tracking code uses to store cookies.
// * You will need to have this script installed on every page.