subicura

# docker stack deploy --compose-file ./docker-stack.yml prom-stack
version: "3"

services:
  prometheus:
    image: prom/prometheus:latest
    networks:
      - monitoring
    ports:
      - 9001:9090

subicura

Http Request Benchmark

간단하게 돌려봄. 정확하지 않을 수 있음. 테스트 할 때마다 값이 달라져서 적당한 추세정도만 확인하는 것으로..

Test

• Host
  • MacBook Pro (Retina, 15-inch, Late 2013)
  • 2.3 GHz Intel Core i7 / 16GB 16000MHz DDR3
• Test Server

subicura

Instructions

• copy the file commit-msg to .git/hooks/commit-msg
• make sure your delete the sample file .git/hooks/commit-msg.sample
• Make commit msg executable. chmod +x .git/hooks/commit-msg
• Edit commit-msg to better fit your development branch, commit regex and error message
• Profit $$

Shell example

subicura

Getting Started with NPM (as a developer)

If you haven't already set your NPM author info, now you should:

npm set init.author.name "Your Name"
npm set init.author.email "[email protected]"
npm set init.author.url "http://yourblog.com"

npm adduser

subicura

# References:
#   http://blog.mixu.net/2011/08/13/nginx-websockets-ssl-and-socket-io-deployment/
#   http://blog.exceliance.fr/2012/09/10/how-to-get-ssl-with-haproxy-getting-rid-of-stunnel-stud-nginx-or-pound/
#

global
    nbproc  2
    maxconn 16384

defaults

subicura

API Response 설계에 대한 가이드 문서입니다.

Status Code와 JSON Response(response body)로 정의합니다.

API 분석 참고

STATUS CODE

• 200 - ok
  • index, show, update, 그외 대부분
• 201 - create
  • create

subicura

Status code 참고

http://guides.rubyonrails.org/layouts_and_rendering.html#the-status-option

자주 사용하는 status code

• 200 - ok
  • request 성공
  • ex) resource 목록/resource 상세/resource 수정/그외 대부분의 API 성공
• 201 - create
  • request 성공
  • ex) resource 생성 성공

subicura

require 'spec_helper'

describe "User Model" do

  context "Association" do
    it { should have_many(:groups) }
  end
  
  context "Validation" do
    it "name과 email속성을 가진다." do