seanh

User Stories

Reading list

• [Mark Shead: Creating Good User Stories][Mark Shead]
• [GOV.UK Service manual: Writing user stories][GOV.UK]
• [Mike Cohn's blog posts about user stories][Mike Cohn]
• [Mike Cohn: User Stories Applied (book)][User Stories Applied]

judy2k

# Pass the env-vars to MYCOMMAND
eval $(egrep -v '^#' .env | xargs) MYCOMMAND
# … or ...
# Export the vars in .env into your shell:
export $(egrep -v '^#' .env | xargs)

ar5had

// mongoose 4.3.x
var mongoose = require('mongoose');
 
/* 
 * Mongoose by default sets the auto_reconnect option to true.
 * We recommend setting socket options at both the server and replica set level.
 * We recommend a 30 second connection timeout because it allows for 
 * plenty of time in most operating environments.
 */
var options = { server: { socketOptions: { keepAlive: 300000, connectTimeoutMS: 30000 } }, 

Nezteb

#!/bin/bash
# Noah Betzen
# Ubuntu 14.04 Basic Setup

#################### VARIABLES TO CHANGE
SSHPORT=22 # change this if you want
WEBPORT=80 # change this if you want
HTTPSPORT=443 # change this if you want
#################### DO NOT EDIT BELOW THIS LINE

lukas-h

Markdown License badges

Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.

Notes

• The badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.

Translations: (No guarantee that the translations are up-to-date)

• 🇫🇷 Cette liste en français

kuldeepJadhav

/**
 * Created by jadhavk on 1/14/15.
 */

// Load all the models
var mongoose = require('mongoose');
mongoose.model('Category', require('../models/category').Category);
mongoose.model('SubCategory', require('../models/category').SubCategory);
mongoose.model('Location', require('../models/location').Location);
mongoose.model('User', require('../models/user').User);

demisx

Angular application directory structure

Leverages Angular UI Router instead of core ngRoute module. UI Router allows us to organize our application interface into a state machine. Unlike the $route service in the Angular ngRoute module, which is organized around URL routes, UI-Router is organized around states, which may optionally have routes, as well as other behavior, attached.

LIFT* Organization principle:

• L - Locating code easy
• I - Identify code at a glance

LeCoupa

// Restify Server CheatSheet.
// More about the API: http://mcavage.me/node-restify/#server-api
// Install restify with npm install restify


// 1.1. Creating a Server.
// http://mcavage.me/node-restify/#Creating-a-Server


var restify = require('restify');

trumbitta

# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j