For 4 servings:
- 125g floor
- 250ml milk
- 1-2 eggs
For 8-10 servings
- 250g floor
- 500ml milk
//- app/views/forgot-password.jade | |
extends ../layouts/default | |
block heading | |
h2.center= title | |
block content | |
br | |
form.form-horizontal.col-md-5.col-md-offset-4(action="/users/forgot-password", method="post", role="form") |
For 4 servings:
For 8-10 servings
var layers = [ | |
{ | |
image: 'image 1', | |
x1: 0, | |
y1: 0, | |
x2: 100, | |
y2: 100 | |
}, | |
{ |
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
// Package GinHTMLRender provides some sugar for gin's template rendering | |
// | |
// This work is based on gin contribs multitemplate render https://github.com/gin-gonic/contrib/blob/master/renders/multitemplate | |
// | |
// Usage | |
// | |
// router := gin.Default() | |
// | |
// // Set html render options | |
// htmlRender := GinHTMLRender.New() |
.PHONY: build doc fmt lint dev test vet godep install bench | |
PKG_NAME=$(shell basename `pwd`) | |
install: | |
go get -t -v ./... | |
build: vet \ | |
test \ | |
go build -v -o ./bin/$(PKG_NAME) |
'use strict'; | |
var gulp = require('gulp'); | |
var sourcemaps = require('gulp-sourcemaps'); | |
var source = require('vinyl-source-stream'); | |
var buffer = require('vinyl-buffer'); | |
var browserify = require('browserify'); | |
var watchify = require('watchify'); | |
var babel = require('babelify'); |