thelbouffi

REQUIREMENTS:
- php-pear (install automatically php7.0-xml and php-xml)
	sudo apt-get install php-pear
-php7.0-mbstring
	sudo apt-get install php7.0-mbstring
-php7.0-dev
	sudo apt-get install php7.0-dev

INSTALLATION:
1- cd /tmp/xxxxxx (e.g: cd /tmp/pear/download)

Gattermeier

// var config = require('./config.js').get(process.env.NODE_ENV);

var config = {
  production: {
    session: {
      key: 'the.express.session.id',
      secret: 'something.super.secret'
    },
    database: 'mongodb://<user>:<pwd>@apollo.modulusmongo.net:27017/db',
    twitter: {

lttlrck

git branch -m old_branch new_branch         # Rename branch locally    
git push origin :old_branch                 # Delete the old branch    
git push --set-upstream origin new_branch   # Push the new branch, set local branch to track the new remote

danharper

// this is the background code...

// listen for our browerAction to be clicked
chrome.browserAction.onClicked.addListener(function (tab) {
	// for the current tab, inject the "inject.js" file & execute it
	chrome.tabs.executeScript(tab.ib, {
		file: 'inject.js'
	});
});

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions