Create a submodule:
git submodule add [email protected]:user/repo.git path/to/module
To change the commit a submodule points to, just move to the commit inside it:
cd path/to/module
Create a submodule:
git submodule add [email protected]:user/repo.git path/to/module
To change the commit a submodule points to, just move to the commit inside it:
cd path/to/module
#!/bin/bash | |
SUDOERS_FILE=/etc/sudoers.d/999-vagrant-cloud-init-requiretty | |
echo 'Defaults:ec2-user !requiretty' > $SUDOERS_FILE | |
echo 'Defaults:root !requiretty' >> $SUDOERS_FILE | |
chmod 440 $SUDOERS_FILE | |
<?php | |
require_once __DIR__.'/vendor/autoload.php'; | |
function bootstrapApplication() | |
{ | |
$app = require __DIR__.'/vendor/laravel/laravel/bootstrap/app.php'; | |
$app->make('Illuminate\Contracts\Console\Kernel')->bootstrap(); |
var async = require('async'), | |
request = require('request'), | |
sprintf = require('sprintf-js').sprintf, | |
pokegoScan = require('pokego-scan'); | |
// coords to check in a loop | |
var coords = { | |
latitude: null, | |
longitude: null | |
}; |
There's been a strange explosion in misinformation about browserify recently, particularly in comparisons to webpack.
Generally speaking, most of this confusion stems from how webpack is more willing to pull features into its core to ease discoverability while browserify is more likely to push features out to userland instead.
I think that longer-term, separability has more benefits from a maintenance and
// attempt to do an async action in a loop, until it doesn't | |
// return an error or a max number of retries is reached. | |
function attempt(opts, fun, next) { | |
var lastError = null, retry = 0, | |
increment = opts.increment || 500, | |
nextTimeout = typeof opts.initial !== 'undefined' ? opts.initial : 500, | |
maxRetries = typeof opts.retries !== 'undefined' ? opts.retries : 0; | |
function nextRetry() { | |
if (maxRetries && retry >= maxRetries) { |
# prune branches deleted in origin
git remote prune origin
# prune tags
# http://stackoverflow.com/questions/1841341/remove-local-tags-that-are-no-longer-on-the-remote-repository
git fetch --prune <remote> '+refs/tags/*:refs/tags/*'
Start of Authority record and authoritative servers of a given domain (see stackoverflow answer):
nslookup -type=soa example.com
Lookup a domain from a particular server. If the DNS server is authoritative for that domain, the response will not be cached (see serverfault answer):
dig @ns1.example.com example.com
#!/usr/bin/env bash | |
# memusg -- Measure memory usage of processes | |
# Usage: memusg COMMAND [ARGS]... | |
# | |
# Author: Jaeho Shin <[email protected]> | |
# Created: 2010-08-16 | |
############################################################################ | |
# Copyright 2010 Jaeho Shin. # | |
# # | |
# Licensed under the Apache License, Version 2.0 (the "License"); # |
To use, go to Taiga's sprint view and paste this code into it. The "User Story" header will be clickable, and will expand or collapse all user stories.