Tom Murphree tmurphree

Definitely not comprehensive. This is meant to be a basic memory aid with links to get more details. I'll add to it over time.

Install

$ npm install mongoose --save

Connect

const mongoose = require('mongoose');

const connectionString = process.env.MONGO_URI || 'mongodb://localhost/databasenamegoeshere';

PostgreSQL

Links

Selected Commands

Command	Description	Link

URL	HTTP Verb	Action
/photos/	GET	index
/photos/new	GET	new
/photos	POST	create
/photos/:id	GET	show
/photos/:id/edit	GET	edit
/photos/:id	PATCH/PUT	update
/photos/:id	DELETE	destroy

Better Jasmine Tests With `this`

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

'Include' in Sequelize: The One Confusing Query That You Should Memorize

When querying your database in Sequelize, you'll often want data associated with a particular model which isn't in the model's table directly. This data is usually typically associated through join tables (e.g. a 'hasMany' or 'belongsToMany' association), or a foreign key (e.g. a 'hasOne' or 'belongsTo' association).

When you query, you'll receive just the rows you've looked for. With eager loading, you'll also get any associated data. For some reason, I can never remember the proper way to do eager loading when writing my Sequelize queries. I've seen others struggle with the same thing.

Eager loading is confusing because the 'include' that is uses has unfamiliar fields is set in an array rather than just an object.

So let's go through the one query that's worth memorizing to handle your eager loading.

The Basic Query

Clean up the whole mess

docker system prune

For the rest, syntax is:

bash
PowerShell

Delete all containers

docker rm $(docker ps -aq)

	var crypto = require("crypto")

	function encrypt(key, data) {
	var cipher = crypto.createCipher('aes-256-cbc', key);
	var crypted = cipher.update(text, 'utf-8', 'hex');
	crypted += cipher.final('hex');

	return crypted;
	}

	# See list of docker virtual machines on the local box
	$ docker-machine ls
	NAME ACTIVE URL STATE URL SWARM DOCKER ERRORS
	default * virtualbox Running tcp://192.168.99.100:2376 v1.9.1

	# Note the host URL 192.168.99.100 - it will be used later!

	# Build an image from current folder under given image name
	$ docker build -t gleb/demo-app .

	That’s one of the real strengths of Docker: the ability to go back to a previous commit. The secret is simply to docker tag the image you want.

	Here’s an example. In this example, I first installed ping, then committed, then installed curl, and committed that. Then I rolled back the image to contain only ping:

	$ docker history imagename
	IMAGE CREATED CREATED BY SIZE
	f770fc671f11 12 seconds ago apt-get install -y curl 21.3 MB
	28445c70c2b3 39 seconds ago apt-get install ping 11.57 MB
	8dbd9e392a96 7 months ago 131.5 MB