Sudharsanan Muralidharan scaffeinate

Add two modules one for api and other for processor(Ensure its a java library) - There are conflicts in javax pacakges between android jar and jdk javax packages.
include apt plugin

apply plugin: 'com.neenbedankt.android-apt' 
buildscript {
  repositories{
    mavenCentral()
   } 
 dependencies{

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

1. Gemfile

gem 'browserify-rails', '1.5.0' # until fix: https://github.com/browserify-rails/browserify-rails/issues/101
gem 'react-rails'

Browserify-rails allows to use browserify within assets pipeline. React-rails is here only to allow to use #react_component (and thus, prerendering).

Note that jquery-rails can be removed from Gemfile, the npm version of jquery and jquery-ujs will be used instead.

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.

	#MMMMMMMMMM$==~~~==+8MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
	#MMMMMMMMM?~==~~~=~==?MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
	#MMMMMMM$+~~~~~~~~~~~=+NMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
	#MMMMMM?=~~~~~~~~~~~~~==+MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
	#MMMMZ===~~~~~~~~~~~~~~~==$MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
	#MMD+~~=~~~~~~~~~~~~~~~~~===MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
	#M+=~~~~~~~~~~~~~~~~~====~~==IMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
	#M++==~~~=~~~~~=~~=~I$$$?~==++?$MMMMMMMMMM ML MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMM
	#M?+++++++======~IZOO8DDDDN7++++?MMMMMMMMM MM

	# Nginx+Unicorn best-practices congifuration guide. Heartbleed fixed.
	# We use latest stable nginx with fresh openssl, zlib and pcre dependencies.
	# Some extra handy modules to use: --with-http_stub_status_module --with-http_gzip_static_module
	#
	# Deployment structure
	#
	# SERVER:
	# /etc/init.d/nginx (1. nginx)
	# /home/app/public_html/app_production/current (Capistrano directory)
	#