onjin

postgres:
  image: postgres:9.4
  volumes:
    - ./init.sql:/docker-entrypoint-initdb.d/init.sql

richardscarrott

An exploration of the different render methods available in react-enzyme.

dtomasi

server {
    listen       80;
    server_name  localhost;
    root       /Users/YOUR_USERNAME/Sites;
 
    access_log  /Library/Logs/default.access.log  main;
 
    location / {
        include   /usr/local/etc/nginx/conf.d/php-fpm;
    }

rvl

Pushing to Multiple Git Repos

If a project has to have multiple git repos (e.g. Bitbucket and Github) then it's better that they remain in sync.

Usually this would involve pushing each branch to each repo in turn, but actually Git allows pushing to multiple repos in one go.

If in doubt about what git is doing when you run these commands, just

pwenzel

Here we use Homebrew to install rbenv:

1. brew update; and brew install rbenv ruby-build
2. Add ~/.rbenv/shims to your PATH
3. Include the contents of completions/rbenv.fish in your Fish config.
4. Run rbenv install 2.2.2 and rbenv rehash
5. Run rbenv global 2.2.2

Now you can run gem install bundler and bundle install within your Ruby project.

ericelliott

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

jakebellacera

/* 
 * CSS Time to Milliseconds
 * by Jake Bellacera (http://jakebellacera.com)
 * ============================================
 * 
 * Converts CSS time into milliseconds. Useful for timing functions around CSS animations.
 * It supports both seconds (s) and milliseconds (ms).
 * 
 * Arguments:
 *   time_string - string representation of a CSS time unit (e.g. "1500ms" or "1.5s")

sevcsik

They say that one of the pros of NodeJS is that you use the same language on the back-end and the front-end, so it's easy to share code between them. This sounds great in theory, but in practice the synchronous dependency handling in NodeJS works completely different than any client-side frameworks (which are asynchronous).

Usually that means that you end up copy-pasting your code between your NodeJS sources and your client-side sources, or you use some tool like Browserify, which is brilliant, but they add an extra step in the build process and most likely will conflict with the dependency handling of the framework of your choice (like AnularJS DI). I couldn't look in the mirror if I would call that code sharing.

Fortunately, with a couple of lines of boilerplate code, you can write a module which works in NodeJS and AngularJS as well without any modification.

No globals in the front-end, and dependencies will work. The isNode and isAngular va

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

webdesserts

// NOTE: I previously suggested doing this through Grunt, but had plenty of problems with
// my set up. Grunt did some weird things with scope, and I ended up using nodemon. This
// setup is now using Gulp. It works exactly how I expect it to and is WAY more concise.
var gulp = require('gulp'),
    spawn = require('child_process').spawn,
    node;

/**
 * $ gulp server
 * description: launch the server. If there's a server already running, kill it.