stephenhardy

-- Remove the history from 
rm -rf .git

-- recreate the repos from the current content only
git init
git add .
git commit -m "Initial commit"

-- push to the github remote repos ensuring you overwrite history
git remote add origin [email protected]:<YOUR ACCOUNT>/<YOUR REPOS>.git

jctosta

Screen Quick Reference

Basic

Description	Command
Start a new session with session name	screen -S <session_name>
List running sessions / screens	screen -ls
Attach to a running session	screen -x
Attach to a running session with name	screen -r

jasondavis

<?php

/*
Example Usage passing in Array of netowrks we want countsa for...

$socialCounts = new socialNetworkShareCount(array(
    'url' => 'http://www.codedevelopr.com/',
    'facebook' => true,
    'twitter' => true,
    'pinterest' => true,

DinoChiesa

function computeHttpSignature(config, headerHash) {
  var template = 'keyId="${keyId}",algorithm="${algorithm}",headers="${headers}",signature="${signature}"',
      sig = template;

  // compute sig here
  var signingBase = '';
  config.headers.forEach(function(h){
    if (signingBase !== '') { signingBase += '\n'; }
    signingBase += h.toLowerCase() + ": " + headerHash[h];
  });

ravibhure

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches, such as upstream/master:

git fetch upstream

lukecampbell

#!/bin/bash
set -e

echo "Creating new OpenSSL Certificate Authority"
echo -n "Enter path to CA [.]: "
read ca_path

ca_path=${ca_path:-$PWD}
if [[ "$ca_path" != /* ]]; then
    ca_path="$PWD/$ca_path"

ageis

security and hardening options for systemd service units

A common and reliable pattern in service unit files is thus:

NoNewPrivileges=yes
PrivateTmp=yes
PrivateDevices=yes
DevicePolicy=closed
ProtectSystem=strict

xiaohutai

In app/config/config.yml:

wysiwyg:
    (...)
    ck:
        (...)
        format_tags: "p;h2;h3;h4;info;warning;error;success"
        format_info: { name: "Info", element: "p", attributes: { 'class': 'info' } }
 format_warning: { name: "Warning", element: "p", attributes: { 'class': 'warning' } }

sportebois

#!/usr/bin/env bash

function ecr-add-tag() {
  if (( $# < 3 )); then
    echo "Wrong number of arguments. Usage:  ecr-add-tag ECR_REPO_NAME TAG_TO_FIND TAG_TO_ADD [AWS_PROFILE]"
    return
  fi
  local repo_name=$1
  local existing_tag=$2
  local new_tag=$3

JamieMason

Group Array of JavaScript Objects by Key or Property Value

Implementation

const groupBy = key => array =>
  array.reduce((objectsByKeyValue, obj) => {
    const value = obj[key];
    objectsByKeyValue[value] = (objectsByKeyValue[value] || []).concat(obj);
    return objectsByKeyValue;