| # show a cyan `OK!`, or arg `1` message | |
| function show_info() | |
| { | |
| local msg="OK!" | |
| if [ ! -z "$1" ]; then | |
| msg="$1" | |
| fi | |
| echo -e "\033[0;36m${msg}\033[0m" | |
| } |
| var gulp = require('gulp'), | |
| sass = require('gulp-sass'), | |
| browserify = require('gulp-browserify'), | |
| concat = require('gulp-concat'), | |
| embedlr = require('gulp-embedlr'), | |
| refresh = require('gulp-livereload'), | |
| lrserver = require('tiny-lr')(), | |
| express = require('express'), | |
| livereload = require('connect-livereload') | |
| livereloadport = 35729, |
| # config valid only for Capistrano 3.1 | |
| lock '3.1.0' | |
| set :application, "" # EDIT your app name | |
| set :scm, :git | |
| set :repo_url, "" # EDIT your git repository | |
| set :keep_releases, 3 |
| from functools import partial | |
| class partialmethod(partial): | |
| def __get__(self, instance, owner): | |
| if instance is None: | |
| return self | |
| return partial(self.func, instance, | |
| *(self.args or ()), **(self.keywords or {})) |
| #!/usr/bin/env ruby | |
| require "digest/md5" | |
| module DPKG | |
| def self.control(deb_package_path) | |
| return `ar p #{deb_package_path} control.tar.gz | tar -xzO` | |
| end | |
| class ScanPackages | |
| def self.scan(path) |
Our Virtual Machines are provisioned using Vagrant from a Linux base box to run using VirutalBox. If the Hard Disk space runs out and you cannot remove files to free-up space, you can resize the Hard Disk using some VirtualBox and Linux commands.
The following steps assume you've got a set-up like mine, where:
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.
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
| ## Making a 32 bit version of Homestead | |
| # Clone the settler repository to a directory | |
| git clone https://github.com/laravel/settler.git Ubuntu32 | |
| # In that directory edit the file called "Vagrantfile" to use a ubuntu 32 box instead of the 64 bit one | |
| change this line: | |
| config.vm.box = "ubuntu/trusty64" |
| #!/usr/bin/env python | |
| # Adapted from Mark Mandel's implementation | |
| # https://github.com/ansible/ansible/blob/devel/plugins/inventory/vagrant.py | |
| import argparse | |
| import json | |
| import paramiko | |
| import subprocess | |
| import sys |
| #!/bin/sh | |
| for LOOPS in $(losetup -a | awk -F':' {'print $1'} | awk -F'/' {'print $3'}); do | |
| for LOOPPART in $(ls /dev/mapper/${LOOPS}*| awk -F'/' {'print $4'}); do | |
| dmsetup remove ${LOOPPART}; | |
| done; | |
| losetup -d /dev/${LOOPS}; | |
| done |