teohm

---

Disclaimer: I'm super new to DynamoDB, so if you found I wrote something incorrect or stupid, just kindly send me a comment :)

---

Learn DynamoDB

• database -> tables -> items -> attributes
• db = a collection of tables

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

renoirb

[client]                                                                                                                                                     
ssl
ssl-ca=/etc/mysql/ca-cert.pem
ssl-cert=/etc/mysql/client-cert.pem
ssl-key=/etc/mysql/client-key.pem

[mysqld]
ssl
ssl-cipher=DHE-RSA-AES256-SHA
ssl-ca=/etc/mysql/ca-cert.pem

tlack

exports.req_ip = function(req) {
        return ( req.headers["X-Forwarded-For"]
                                        || req.headers["x-forwarded-for"]
                                        || req.client.remoteAddress );
}

ramontayag

#!/usr/bin/env ruby
LIMIT=30 #limit on seconds
PROCESS="convert" #change to process u want to grep
COMMAND="ps -eo pid,cmd,etime"

process_list = `#{COMMAND} | grep #{PROCESS}`
process_list = process_list.split("\n") # make an array of process strings
process_list = process_list.select {|process| process !~ /grep/} # remove the grep process

process_list.each do |process|