Ranielly Ferreira raniellyferreira

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

createElement.js

createElement.js lets document.createElement use CSS selectors.

This is a pretty useful library for building out DOM elements. The whole thing runs on one regex and a for loop, so it’s plenty fast. The script is 300 bytes when compressed and gzipped. For 524 bytes (advanced), it includes nesting support and can generate entire DOM hierarchies, including text nodes.

Usage

document.createElement(); // generates <div />

Awesome PHP

A curated list of amazingly awesome PHP libraries, resources and shiny things.

	-- a quick LUA access script for nginx to check IP addresses against an
	-- `ip_blacklist` set in Redis, and if a match is found send a HTTP 403.
	--
	-- allows for a common blacklist to be shared between a bunch of nginx
	-- web servers using a remote redis instance. lookups are cached for a
	-- configurable period of time.
	--
	-- block an ip:
	-- redis-cli SADD ip_blacklist 10.1.1.1
	-- remove an ip:

	user www-data;

	#worker_processes 4;
	#worker_priority 0;
	#worker_cpu_affinity 0001 0010 0100 1000;
	#worker_rlimit_nofile 163840;

	#worker_processes 8;
	#worker_priority 0;
	#worker_cpu_affinity 00000001 00000010 00000100 00001000 00010000 00100000 01000000 10000000;