mtigas

Client-side SSL

For excessively paranoid client authentication.

---

Updated Apr 5 2019:

because this is a gist from 2011 that people stumble into and maybe you should AES instead of 3DES in the year of our lord 2019.

some other notes:

mathebox

import math

def rgb_to_hsv(r, g, b):
    r = float(r)
    g = float(g)
    b = float(b)
    high = max(r, g, b)
    low = min(r, g, b)
    h, s, v = high, high, high

JeffBelback

#!/bin/bash
# Stop all containers
containers=`docker ps -a -q`
if [ -n "$containers" ] ; then
        docker stop $containers
fi
# Delete all containers
containers=`docker ps -a -q`
if [ -n "$containers" ]; then
        docker rm -f -v $containers

x3rAx

# +----------------------------+
# |         IDE files          |
# +----------------------------+
/.idea


# +----------------------------+
# |          Vagrant           |
# +----------------------------+
/.vagrant

fmasuhr

1. Run the following command and copy the ID of your VM

VBoxManage list vms
=> "virtualMachine" {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

2. Go to the Vagrant project configuration folder

luizventurote

• Use VBoxManage list vms to get VM id
• Open folder .vagrant/machines/default/virtualbox
• Set the new ID on files action_provision and id
• Remove SSH connection on Vagrantfile

config.ssh.insert_key = false
config.ssh.username = 'vagrant'
config.ssh.password = 'vagrant'

krambertech

import React, { Component } from 'react';

import TextField from 'components/base/TextField';

const WAIT_INTERVAL = 1000;
const ENTER_KEY = 13;

export default class TextSearch extends Component {
    constructor(props) {
        super();

A-gambit

Proposal for a lightning talk at the Reactive 2016.

Keep calm and like/retweet it on Twitter and star this Gist to vote on this talk.

Road from UndefinedLand

I work at Grammarly. We like React and happily use it in our applications. However, sometimes something goes wrong and bugs creep into the code. Here comes testing. It helps make us confident about the quality of our code.

jpierson

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

1. Clone some repo (you've probably already done this step)

   git clone [email protected]

alexeiz

#!/usr/bin/env python

import sys
import pyautogui
from datetime import datetime, timedelta

def move_rel(dx, dy, dur):
    pyautogui.moveRel(dx, dy, dur, pyautogui.easeInQuad)

def square(side, dur):