zthomas

// License: MIT, feel free to use it!

const Intercom = require('intercom-client');
const appId = 'APP_ID'
const apiKey = 'APP_KEY'
const client = new Intercom.Client(appId, apiKey);
const async = require('async-q')

//REF: https://developers.intercom.com/reference#iterating-over-all-users
//WARNING: you can only have one scroll working at once. you need to wait for that scroll to clear to try again

ZwodahS

#!/bin/bash
# source http://stackoverflow.com/questions/23222616/copy-all-keys-from-one-db-to-another-in-redis
#set connection data accordingly
source_host=localhost
source_port=6379
source_db=1
target_host=localhost
target_port=6379
target_db=2

spalladino

# Backup
docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql

# Restore
cat backup.sql | docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE

gullitmiranda

systems({
  "my-app": {
    image: {"docker": "azukiapp/php-fpm"},
    provision: [
      // "composer install",
    ],
    workdir: "/azk/#{manifest.dir}",
    mounts: {
      '/azk/#{manifest.dir}': path("."),
      '/etc/nginx/sites-enabled/nginx_public.conf': path("./nginx_public.conf")

JuanitoFatas

Downloading https://github.com/wayneeseguin/rvm/archive/1.26.9.tar.gz
curl: (23) Failed writing body (0 != 861)

Could not download 'https://github.com/wayneeseguin/rvm/archive/1.26.9.tar.gz'.
  curl returned status '23'.

Downloading https://bitbucket.org/mpapis/rvm/get/1.26.9.tar.gz
curl: (23) Failed writing body (0 != 15973)

Could not download 'https://bitbucket.org/mpapis/rvm/get/1.26.9.tar.gz'.

ryanflorence

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

ryanflorence

.
├── actions
├── stores
├── views
│   ├── Anonymous
│   │   ├── __tests__
│   │   ├── views
│   │   │   ├── Home
│   │   │   │   ├── __tests__
│   │   │   │   └── Handler.js

andyshinn

Deploying Deis on AWS

These instructions will get you up and running with Deis and CoreOS in a AWS VPC. There already exists a CloudFormation script to get up and running in AWS. But if you want to get down and dirty, this document will help walk you through the steps.

I tried to build these instructions for both the AWS web console and equivilent AWS CLI. If you find errors, please feel free to comment so I can update them. You can also find me in the #deis IRC channel on Freenode if you have questions.

AWS

Since we will be running CoreOS and Deis inside a VPC we need some AWS setup first. We need a single subnet VPC, some security groups, and instances of CoreOS.

ericsaboia

if (config.admin.email) {
  process.on('uncaughtException', function(err) {
    console.log(err.stack);
    nodemailer.createTransport("SMTP", {
        service: "Sendgrid"
      , auth: {
          user: config.smtp.username
        , pass: config.smtp.password
      }
    }).sendMail({

jlecour

# encoding: UTF-8

require 'optparse'
require 'net/http'
require 'json'

def parse_options(argv)
  opts = {}

  @parser = OptionParser.new do |o|