Add masochist memory check to monit

[wincent]

There might be an underlying memory leak here to hunt down, but I just learned a few things:

• A deploy was failing when gulp build was dying with a 137 exit status.
• 137 is actually 128 + 9, which means the process did not exit normally via exit() but was sent a -9 signal from another process.
• /var/log/messages shows it was, of course, the OOM killer.
• The masochist Node.js process had grown to several hundred meg, and the t2.micro instance only has a gig.

So, restarted the masochist process; on fresh boot it occupies about 85 meg. Then deploy worked just fine.