callumacrae

List of JavaScript Build Tools

Yet another framework syndrome

Name	Date	URL	Stars
Jake	April 2010	https://github.com/mde/jake	1000
Brunch	January 2011	http://brunch.io/	3882
smoosh	March 2011	https://github.com/fat/smoosh	329
anvil.js	February 2012	https://github.com/anviljs/anvil.js	161

olivierlacan

• http://david.heinemeierhansson.com/2014/tdd-is-dead-long-live-testing.html
• http://blog.8thlight.com/uncle-bob/2014/04/25/MonogamousTDD.html
• http://david.heinemeierhansson.com/2014/test-induced-design-damage.html
• http://blog.8thlight.com/uncle-bob/2014/05/01/Design-Damage.html
• http://david.heinemeierhansson.com/2014/slow-database-test-fallacy.html
• http://blog.8thlight.com/uncle-bob/2014/04/30/When-tdd-does-not-work.html
• https://www.destroyallsoftware.com/blog/2014/tdd-straw-men-and-rhetoric
• http://articles.coreyhaines.com/posts/active-record-spec-helper/
• http://martinfowler.com/bliki/UnitTest.html

sheerun

# Generates necessary certificates to ~/.docker
#
# Usage:
#   bundle install
#   ruby certgen.rb <domain>

require 'certificate_authority'
require 'fileutils'

if ARGV.empty?

stevenyap

You have a git commit in your history that is causing a bug but you do not know which commit it is.
Here's how to use git bisect to find the commit that causes the bug.

# in the git root, start the git bisect
git bisect start

# mark current commit as bad
git bisect bad

manfromanotherland

<form id="contact-form" action="//formspree.io/[email protected]" method="post">
	<input type="text" name="Name" placeholder="Name" required>
	<input type="email" name="Email" placeholder="Email" required>
	<textarea name="Message" cols="30" rows="6" placeholder="Message" required></textarea>
	<!-- CONFIG -->
	<input class="is-hidden" type="text" name="_gotcha">
	<input type="hidden" name="_subject" value="Subject">
	<input type="hidden" name="_cc" value="[email protected]">
	<!-- /CONFIG -->
	<input class="submit" type="submit" value="Send">

magnetikonline

AWS Elastic Beanstalk deploy user restricted IAM policy

An IAM user policy document to give minimal rights for deploying an Elastic Beanstalk application.

Where:

• REGION: AWS region.
• ACCOUNT_ID: AWS account ID.
• APPLICATION_NAME: Desired target Elastic Beanstalk application name(space).
• IAM_INSTANCE_PROFILE_ROLE: The instance profile (IAM role) Elastic Beanstalk EC2 instaces will run under.

iamralch

import (
	"archive/tar"
	"fmt"
	"io"
	"os"
	"path/filepath"
	"strings"
)

func tarit(source, target string) error {

RobertoSchneiders

I am deploying with this IAM using Codeship and Circle CI to Elastic Beanstalk. I had a lot of trouble with this config. I talked to the aws support for about 6 hours until this worked properly, so, I guess it is worth to share.

UPDATE: In the end, I have to use the AWSElasticBeanstalkFullAccess policy. My custom policy keep breaking every week with some new added permission or some EB internal change. Anyway, the IAM I was using is below.

This works for me with CircleCI and EB Cli.

{
    "Version": "2012-10-17",
    "Statement": [
        {

jeffweiss

defmodule MyApp.Mixfile do
  use Mix.Project

  def project do
    [app: :my_app,
     version: get_version,
     elixir: "~> 1.0",
     elixirc_paths: elixirc_paths(Mix.env),
     compilers: Mix.compilers,
     build_embedded: Mix.env == :prod,

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