pixelhandler

var application_root = __dirname,
    express = require("express"),
    path = require("path"),
    mongoose = require('mongoose');

var app = express.createServer();

// database

mongoose.connect('mongodb://localhost/ecomm_database');

hellerbarde

Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs

Halleck45

<?xml version="1.0" ?>
<project name="audit" basedir="." default="audit">
    
    <property name="style" value="ZEND" />
    <property name="test" value="${source}/../test" />
    <property name="test-bootstrap" value="" />
    
    <target name="prepare">
        <mkdir dir="${out}" />
    </target>

mashpie

// require modules
var http = require('http'),
    i18n = require('i18n'),
    app;

// minimal config
i18n.configure({
  locales: ['en', 'de'],
  directory: __dirname + '/locales'
});

pboos

configurations {
    apt
}

dependencies {
    compile 'com.squareup.dagger:dagger:1.1.0'
    apt 'com.squareup.dagger:dagger-compiler:1.1.0'
}

android.applicationVariants.all { variant ->

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

shakalaca

buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:0.5.6'
    }
}

task wrapper(type: Wrapper) {

markgoodyear

/*!
 * gulp
 * $ npm install gulp-ruby-sass gulp-autoprefixer gulp-cssnano gulp-jshint gulp-concat gulp-uglify gulp-imagemin gulp-notify gulp-rename gulp-livereload gulp-cache del --save-dev
 */

// Load plugins
var gulp = require('gulp'),
    sass = require('gulp-ruby-sass'),
    autoprefixer = require('gulp-autoprefixer'),
    cssnano = require('gulp-cssnano'),

stefanhoth

android {
  
    // .. set up build flavors etc here
    
    //instead of "app-release.apk" this method will rewrite the name to
    // "MyCoolCompany-MyGreatProduct-v<defaultConfig.versionName>-RELEASE.apk which is much better suited for archiving and overall handling
    // To restore the default behavior just delete the whole block below
    applicationVariants.all { variant ->

        def apk = variant.outputFile;

sanderpotjer

<?php
/**
 * @package	Article Form override for Joomla 3
 * @copyright 	Copyright (c) 2014 Sander Potjer - www.perfectwebteam.nl
 * @license 	GNU General Public License version 3 or later
 */

defined('_JEXEC') or die;

JHtml::_('behavior.keepalive');