lehtu

From Meteor's documentation:

In Meteor, your server code runs in a single thread per request, not in the asynchronous callback style typical of Node. We find the linear execution model a better fit for the typical server code in a Meteor application.

This guide serves as a mini-tour of tools, trix and patterns that can be used to run async code in Meteor.

Basic async

Sometimes we need to run async code in Meteor.methods. For this we create a Future to block until the async code has finished. This pattern can be seen all over Meteor's own codebase:

lehtu

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

lehtu

// working demo in here: https://jsfiddle.net/lehtu/awnuk9f1/

var moment = require('moment');

var start = '2016-01-01';
var end = '2016-12-31';
var weeks = moment(end).diff(start, 'week');
var dates = [];

for (var i = 0; i <= weeks; i++) {

lehtu

Counts how many items exists in db.orders.products array.

Inside aggregate query you only need to chance $products to be the property which contains an array

db.orders.aggregate([{$project: {item: 1, bookings: {$size:"$products"}}}])

lehtu

{
    "extends": [
      "airbnb",
      "plugin:meteor/recommended"
    ],
    "plugins": [
        "import",
        "meteor"
 ],

lehtu

*.swp
*~
*.iml
.*.haste_cache.*
.DS_Store
.idea
.babelrc
.eslintrc
npm-debug.log
lib

lehtu

How to setup linting in pre-commit (only for staged files)

First we need to get list of staged files.

git status -s -uno

Then we want to limit it only to list of files.

git status -s -uno | grep -o -e '[a-zA-Z0-9_.-]*.js'

lehtu

LEMP Server on Ubuntu 14.04

For detail look here

Update timezone

sudo dpkg-reconfigure tzdata

Add user and prevent root login

lehtu

Partial Command History for Git BASH

Partial Command History is pretty basic in any *NIX system, but for some reason in Git BASH it's not a default.

What does partial command history mean?

This means that when you type partial command in bash and use arrow up/down keys, it goes through only those commands starting with what you have already typed.

How to:

In your ~/.inputrc file you just need to add key bindings:

lehtu

Problem

Git for Windows slows down a lot after network change or after use of an VPN. For example ls or git status commands took over a minute to complete!

Observations

During this slow pace if network is turned off, then git-bash works normally.

Git for Windows uses __git_ps1 internally for getting some info and that alone takes over a minute!