GUI

#!/bin/bash
# Script for placing sudoers.d files with syntax-checking

# Making a temporary file to contain the sudoers-changes to be pre-checked
TMP=$(mktemp -t vagrant_sudoers)
cat /etc/sudoers > $TMP
cat >> $TMP <<EOF

# Allow passwordless startup of Vagrant when using NFS.
Cmnd_Alias VAGRANT_EXPORTS_ADD = /usr/bin/su root -c echo '*' >> /etc/exports

yctay

namespace :figaro do
  desc "SCP transfer figaro configuration to the shared folder"
  task :setup do
    transfer :up, "config/application.yml", "#{shared_path}/application.yml", :via => :scp
  end

  desc "Symlink application.yml to the release path"
  task :finalize do
    run "ln -sf #{shared_path}/application.yml #{release_path}/config/application.yml"
  end

sindresorhus

#!/usr/bin/env bash
# MIT © Sindre Sorhus - sindresorhus.com

# git hook to run a command after `git pull` if a specified file was changed
# Run `chmod +x post-merge` to make it executable then put it into `.git/hooks/`.

changed_files="$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)"

check_run() {
	echo "$changed_files" | grep --quiet "$1" && eval "$2"

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

jlecour

# encoding: UTF-8

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

def parse_options(argv)
  opts = {}

  @parser = OptionParser.new do |o|

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({

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.

ryanflorence

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

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.

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'.