Son Dang sondnm

OAUTH2

The Problem

I’m a web app that wants to allow other web apps access to my users’ information, but I want to ensure that the user says it’s ok.

The Solution

I can’t trust the other web apps, so I must interact with my users directly. I’ll let them know that the other app is trying to get their info, and ask whether they want to grant that permission. Oauth defines a way to initiate that permission verification from the other app’s site so that the user experience is smooth. If the user grants permission, I issue an AuthToken to the other app which it can use to make requests for that user's info.

Note on encryption

Oauth2 has nothing to do with encryption -- it relies upon SSL to keep things (like the client app’s shared_secret) secure.

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

PROCESS STATE CODES

Here are the different values that the s, stat and state output specifiers (header "STAT" or "S") will display to describe the state of a process.

CODE	Meaning
D	Uninterruptible sleep (usually IO)
R	Running or runnable (on run queue)
S	Interruptible sleep (waiting for an event to complete)
T	Stopped, either by a job control signal or because it is being traced.
W	paging (not valid since the 2.6.xx kernel)

If you have two days to learn the very basics of modelling, Domain-Driven Design, CQRS and Event Sourcing, here's what you should do:

In the evenings read the [Domain-Driven Design Quickly Minibook]{http://www.infoq.com/minibooks/domain-driven-design-quickly}. During the day watch following great videos (in this order):

Eric Evans' [What I've learned about DDD since the book]{http://www.infoq.com/presentations/ddd-eric-evans}
Eric Evans' [Strategic Design - Responsibility Traps]{http://www.infoq.com/presentations/design-strategic-eric-evans}
Udi Dahan's [Avoid a Failed SOA: Business & Autonomous Components to the Rescue]{http://www.infoq.com/presentations/SOA-Business-Autonomous-Components}
Udi Dahan's [Command-Query Responsibility Segregation]{http://www.infoq.com/presentations/Command-Query-Responsibility-Segregation}
Greg Young's [Unshackle Your Domain]{http://www.infoq.com/presentations/greg-young-unshackle-qcon08}
Eric Evans' [Acknowledging CAP at the Root -- in the Domain Model]{ht

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "[email protected]"

	# This is a skeleton for testing models including examples of validations, callbacks,
	# scopes, instance & class methods, associations, and more.
	# Pick and choose what you want, as all models don't NEED to be tested at this depth.
	#
	# I'm always eager to hear new tips & suggestions as I'm still new to testing,
	# so if you have any, please share!
	#
	# @kyletcarlson
	#
	# This skeleton also assumes you're using the following gems:

	##################################################################
	# /etc/elasticsearch/elasticsearch.yml
	#
	# Base configuration for a write heavy cluster
	#

	# Cluster / Node Basics
	cluster.name: logng

	# Node can have abritrary attributes we can use for routing

	## Prepare ###################################################################

	# Remove RVM
	rvm implode

	# Ensure your homebrew is working properly and up to date
	brew doctor
	brew update

	## Install ###################################################################

	# in spec/support/omniauth_macros.rb
	module OmniauthMacros
	def mock_auth_hash
	# The mock_auth configuration allows you to set per-provider (or default)
	# authentication hashes to return during integration testing.
	OmniAuth.config.mock_auth[:twitter] = {
	'provider' => 'twitter',
	'uid' => '123545',
	'user_info' => {
	'name' => 'mockuser',

	# WAIT! Do consider that `wait` may not be needed. This article describes
	# that reasoning. Please read it and make informed decisions.
	# https://www.varvet.com/blog/why-wait_until-was-removed-from-capybara/

	# Have you ever had to sleep() in Capybara-WebKit to wait for AJAX and/or CSS animations?

	describe 'Modal' do

	should 'display login errors' do
	visit root_path