Wes Johnson sterlingwes

###The Issue With Forever Forever is great for running node services, with a minor setback: the word "forever" doesn't apply to system reboots.

###The solution, run node apps as a system service logged in as root

vim /etc/init/node-app.conf

Contents for node-app.conf

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

Strip HTML Attributes

<([a-z][a-z0-9]*)[^>]*?(/?)>

token	explanation
<	match `<` at beginning of tags
(	start capture group `$1` - tag name
[a-z]	match `a` through `z`

Tutorial: Meteor in Windows using Vagrant

BEFORE YOU CONTINUE:

Now, Meteor runs in any Windows without any line of this tutorial. Just download the Meteor binary! Yay!!
mrt is no longer used with Meteor 1.0

These days some people were discussing at meteor-talk group about running Meteor at Windows and I’ve recommended them using Vagrant. It’s a very developer-friendly piece of software that creates a virtual machine (VM) which let you run any operating system wanted and connect to it without big efforts of configuration (just make the initial installation and you have it working).

Many packages (I've tested) for running Meteor+Vagrant fails because Meteor writes its mongodb file and also other files inside local build folder into a shared folder between the Windows host and the Linux guest, and it simply does not work. So I've put my brain to work and found a solution: do symlinks inside the VM (but do not use ln. Use mount so git can follow it). It’s covered on

Javascript `log` Function

Every time I start a new project, I want to pull in a log function that allows the same functionality as the console.log, including the full functionality of the Console API.

There are a lot of ways to do this, but many are lacking. A common problem with wrapper functions is that the line number that shows up next to the log is the line number of the log function itself, not where log was invoked. There are also times where the arguments get logged in a way that isn't quite the same as the native function.

This is an attempt to once and for all document the function that I pull in to new projects. There are two different options:

The full version: Inspired by the plugin in HTML5 Boilerplate. Use this if you are writing an application and want to create a window.log function. Additionally,

	/**
	* A directive to hide the tags input when the max tags limit is reached.
	* Works with github.com/mbenford/ngTagsInput
	*/
	angular.module('dz.restrictToMaxTags', ['ngTagsInput']).directive( 'restrictToMaxTags', function () {
	var KEY_BACKSPACE = 8
	KEY_TAB = 9;

	return {
	require: 'ngModel',

	var clipboard = require('child_process').spawn('pbcopy')
	, data = 'put whatever data here';

	clipboard.stdin.write(data);
	clipboard.stdin.end();

	- name: ensure github.com is a known host
	lineinfile:
	dest: /root/.ssh/known_hosts
	create: yes
	state: present
	line: "{{ lookup('pipe', 'ssh-keyscan -t rsa github.com') }}"
	regexp: "^github\\.com"

	#!upstart
	description "nodemon server for myapp"
	author "ubuntu"

	start on startup
	stop on shutdown

	script
	export HOME="/home/ubuntu/git/myapp"