lecaoquochung

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

lecaoquochung

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

lecaoquochung

require 'json'
require 'open-uri'
require 'csv'
require 'date'

# Github credentials to access your private project
USERNAME="myusername"
PASSWORD="mypassword"

# Project you want to export issues from

lecaoquochung

Local SSL websites on Mac OSX

These instructions will guide you through the process of setting up local, trusted websites on your own computer.

These instructions are intended to be used on Mac OSX Yosemite.

NOTE: You may substitute the edit command for nano, vim, or whatever the editor of your choice is. Personally, I forward edit to Sublime Text:

alias edit="/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl"

lecaoquochung

var page = require('webpage').create();

page.onConsoleMessage = function (msg) {
    console.log('From Page Console: '+msg);
};

page.onInitialized = function() {
	page.evaluate(function () {
		"use strict";
		//The Referrer we want to set

lecaoquochung

var system = require('system');

// Exit in case of wrong parameter count.
if (system.args.length !== 3) {
    console.log('Usage: scriptname targetUrl referrer');
    console.log('example: $> phantomjs fake-referrer.phantom.js http://example.com http://referrer.example.com');
	phantom.exit();
}

// Set the important pieces