homam

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

// For dev purposes only
AWS.config.update({ accessKeyId: '...', secretAccessKey: '...' });

// Read in the file, convert it to base64, store to S3
fs.readFile('del.txt', function (err, data) {
  if (err) { throw err; }

epochblue

#!/usr/bin/env bash
# TODO: Document this
#
# AUTHOR: Bill Israel [https://github.com/epochblue]
# LICENSE: Public Domain

BOOMDB_DEFAULT="$HOME/.boomdb"
BOOMDB=${BOOMDB:=$BOOMDB_DEFAULT}

# Ensure the DB file exists

blakewest

General

• Are all vars used somewhere?
• Do the vars have properly cased, and meaningful names?
• Style looks appropriate
• No unnecessarily duplicated logic
• Code intent is clear upon initial reading
• Any code that isn't clear, but is needed, has an effective comment
• Are method calls or attribute lookups every called on entities that could be undefined/null?
• The functions can appropriately handle unexpected inputs.
• Commented code has been removed (comments themselves are fine).

epochblue

"""
An afternoon distraction by Bill Israel.

`hipchat-music.py` will send a notification to a HipChat chat room with the
artist and song title of the currently playing song. Supported music apps
include iTunes, Rdio, and Spotify.

_Note: This code uses v2 of the HipChat API._

Requirements:

JoshuaEstes

README

These are the default files that I will usually start with when setting up a symfony2 project to use vagrant and puppet. I'm putting this readme file here for future updates.

Usage

Make sure the files that end in .sh are executable.

Kartones

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

• -E: will describe the underlaying queries of the \ commands (cool for learning!)
• -l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

brock

#!/bin/bash
# node-reinstall
# credit: http://stackoverflow.com/a/11178106/2083544

## program version
VERSION="0.0.13"

## path prefix
PREFIX="${PREFIX:-/usr/local}"

tracker1

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

• lib/ is intended for code that can run as-is
• src/ is intended for code that needs to be manipulated before it can be used

domenic

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

• It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
• It is free, with no quotas.
• Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

sebmarkbage

import { Component } from "React";

export var Enhance = ComposedComponent => class extends Component {
  constructor() {
    this.state = { data: null };
  }
  componentDidMount() {
    this.setState({ data: 'Hello' });
  }
  render() {