derzorngottes

## How to hide API keys from github ##

1. If you have already pushed commits with sensitive data, follow this guide to remove the sensitive info while 
retaining your commits: https://help.github.com/articles/remove-sensitive-data/

2. In the terminal, create a config.js file and open it up:

touch config.js
atom config.js

PaulMorel

'use strict';

// ----------------------------------------------------------------------------
// Base Paths
// ----------------------------------------------------------------------------

var config = {
    projectName: 'Proj',
    browserSync: true,
    basePath: {

mdp

let sources = {
  'default-src': ['\'self\''],
  'script-src': ['\'self\'','https://*.myexternalcdn.com'],
  'frame-src': ['https://someexternalframesource.com'],
  'img-src': ['\'self\'', 'https:', 'data:'],
  'style-src': ['\'self\'', 'https:'],
  'font-src': ['\'self\'', 'https:'],
  'connect-src': ['\'self\''],
}

olivierlacan

This guide assumes that you recently run brew upgrade postgresql and discovered to your dismay that you accidentally bumped from one major version to another: say 9.3.x to 9.4.x. Yes, that is a major version bump in PG land.

First let's check something.

brew info postgresql

The top of what gets printed as a result is the most important:

branneman

/**
 * @param {Event} evt
 * @return {Object}
 */
function getMousePosition(evt) {

  var pageX = evt.pageX;
  var pageY = evt.pageY;
  if (pageX === undefined) {
    pageX = evt.clientX + document.body.scrollLeft + document.documentElement.scrollLeft;

adon-at-work

var AWS = require('aws-sdk'),
    fs = require('fs');

// http://docs.aws.amazon.com/AWSJavaScriptSDK/guide/node-configuring.html#Credentials_from_Disk
AWS.config.loadFromPath('./aws-config.json');

// assume you already have the S3 Bucket created, and it is called ierg4210-shopxx-photos
var photoBucket = new AWS.S3({params: {Bucket: 'ierg4210-shopxx-photos'}});

function uploadToS3(file, destFileName, callback) {

brianmacarthur

var express = require('express');
var cookieParser = require('cookie-parser');
var session = require('express-session');
var flash = require('express-flash');
var handlebars = require('express-handlebars')

var app = express();
var sessionStore = new session.MemoryStore;

// View Engines

nickcernis

<?php // add everything except for this opening line to your functions file

add_filter( 'wp_nav_menu_items', 'sp_add_loginout_link', 10, 2 );

function sp_add_loginout_link( $items, $args ) {
	// Change 'primary' to 'secondary' to put the login link in your secondary nav bar.
	if ( $args->theme_location != 'primary' ) {
		return $items;
	}
	

barbwiredmedia

<?php echo paginate_links( $args ); ?>

<!--OR--> 
<?php
//custom paginaiton with styling from bootstrap
function custom_pagination() {
    global $wp_query;
    $big = 999999999; // need an unlikely integer
    $pages = paginate_links( array(
            'base' => str_replace( $big, '%#%', esc_url( get_pagenum_link( $big ) ) ),

pixeline

# 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