Musale Martin musale

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

Title

<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>

URL

<The URL Structure (path only, no root url)>
Method:

	import logging
	import sys
	from unittest.mock import patch # reqs. python 3. change to from mock if p2.

	from django.conf.urls import url
	from django.http import HttpResponse
	from django.test import TestCase
	from .urls import urlpatterns

	## test assumes a bare django project created called "myproj"

	from twisted.internet import defer, reactor
	from twisted.web.client import getPage

	def listCallback(results):
	print results

	def finish(ign):
	reactor.stop()

	def test():

	# Committing changes to a repo via the Github API is not entirely trivial.
	# The five-step process is outlined here:
	# http://developer.github.com/v3/git/
	#
	# Matt Swanson wrote a blog post translating the above steps into actual API calls:
	# http://swanson.github.com/blog/2011/07/23/digging-around-the-github-api-take-2.html
	#
	# I was not able to find sample code for actually doing this in Ruby,
	# either via the HTTP API or any of the gems that wrap the API.
	# So in the hopes it will help others, here is a simple function to

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048