Feature/3 api posts

app/controllers/v1/posts_controller.rb

@@ -0,0 +1,44 @@
+class V1::PostsController < V1::BaseController
+  before_action :load_post, only: [:update, :show, :destroy]
+
+  def index
+    @posts = Post.all
+    render json: template_respone(200, "Get list post successfully", @posts)
+  end
+
+  def show
+    render json: template_respone(200, "Get post successfully", @post)
+  end
+
+  def create
+    @post = Post.create!(post_params)
+    render json: template_respone(200, "Create post successfully", @post)
+  end
+
+  def update
+    @post.update_attributes(post_params)
+    render json: template_respone(200, "Update post successfully", @post)
+  end
+
+  def destroy
+    @post.destroy
+    render json: template_respone(200, "Destroy post successfully", @post)
+  end
+
+  private
+  def load_post
+    @post = Post.find(params[:id])
+  end
+
+  def post_params
+    params.permit(:title, :content)
+  end
+
+  def template_respone(code, message,result)
+    {
+      code: code,
+      message: message,
+      result: result
+    }
+  end
+end

app/models/post.rb

@@ -0,0 +1,3 @@
+class Post < ActiveRecord::Base
+  validates :title, :content, presence: true
+end

config/routes.rb

@@ -1,5 +1,6 @@
 Rails.application.routes.draw do
 
   api_version(:module => "V1", :path => {:value => "v1"}) do
+    resources :posts
   end
 end

db/migrate/20150917150440_create_posts.rb

@@ -0,0 +1,10 @@
+class CreatePosts < ActiveRecord::Migration
+  def change
+    create_table :posts do |t|
+      t.string :title
+      t.string :content
+
+      t.timestamps null: false
+    end
+  end
+end

db/schema.rb

@@ -0,0 +1,23 @@
+# encoding: UTF-8
+# This file is auto-generated from the current state of the database. Instead
+# of editing this file, please use the migrations feature of Active Record to
+# incrementally modify your database, and then regenerate this schema definition.
+#
+# Note that this schema.rb definition is the authoritative source for your
+# database schema. If you need to create the application database on another
+# system, you should be using db:schema:load, not running all the migrations
+# from scratch. The latter is a flawed and unsustainable approach (the more migrations
+# you'll amass, the slower it'll run and the greater likelihood for issues).
+#
+# It's strongly recommended that you check this file into your version control system.
+
+ActiveRecord::Schema.define(version: 20150917150440) do
+
+  create_table "posts", force: :cascade do |t|
+    t.string   "title",      limit: 255
+    t.string   "content",    limit: 255
+    t.datetime "created_at",             null: false
+    t.datetime "updated_at",             null: false
+  end
+
+end

test/fixtures/posts.yml

@@ -0,0 +1,9 @@
+# Read about fixtures at http://api.rubyonrails.org/classes/ActiveRecord/FixtureSet.html
+
+one:
+  title: MyString
+  content: MyString
+
+two:
+  title: MyString
+  content: MyString

test/functional/v1/posts_controller_test.rb

@@ -0,0 +1,9 @@
+require 'test_helper'
+
+class V1::PostsControllerTest < ActionController::TestCase
+
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

test/integration/v1/posts_controller_test.rb

@@ -0,0 +1,9 @@
+require 'test_helper'
+
+class V1::PostsControllerTest < ActionDispatch::IntegrationTest
+
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

test/models/post_test.rb

@@ -0,0 +1,7 @@
+require 'test_helper'
+
+class PostTest < ActiveSupport::TestCase
+  # test "the truth" do
+  #   assert true
+  # end
+end