Marco Galassi officer-rosmarino

Alternatives to the "Atlassian Stack"

Fuller stack alternatives (replaces at least two of the Atlassian stack)

What are Migrations

Just like how we use Git to version control source code, we use migrations to manage the state of our database schemas.

I'm not really sure what that means...

Imagine you're working on project with another developer, and you're both tasked with creating a specific part of an event planning application. Let's say you are in charge of creating the Users and your friend is going to create the Events.

Let's say you and your friend divided the work in a way so that neither of you will have to to use each other's code to finish your tasks. While you're working on your part of the application, you only really need to touch the Users table when you are working with the database.

Creating models and migrations

	/* VT100 terminal reset (<ESC>c) */

	console.log('\033c');

	/* numbers comparations */

	> '2' == 2
	true

	> '2' === 2

	// Promise.all is good for executing many promises at once
	Promise.all([
	promise1,
	promise2
	]);

	// Promise.resolve is good for wrapping synchronous code
	Promise.resolve().then(function () {
	if (somethingIsNotRight()) {
	throw new Error("I will be rejected asynchronously!");

	var http = require('http');
	var url = require('url');

	var proxy = http.createServer(function(req, res) {
	var request = url.parse(req.url);
	options = {
	host: request.hostname,
	port: request.port \|\| 80,
	path: request.path,
	method: req.method,