distribute_tree 0.0.1

data/distribute_tree.gemspec

@@ -0,0 +1,32 @@
+# encoding: UTF-8
+
+Gem::Specification.new do |s|
+  s.name        = 'distribute_tree'
+  s.version     = '0.0.1'
+  s.date        = '2013-12-04'
+  s.summary     = File.read("README.markdown").split(/===+/)[1].strip.split("\n")[0]
+  s.description = s.summary
+  s.authors     = ["mvj3", "ukisami", "renchaorevee"]
+  s.email       = 'mvjome@gmail.com'
+  s.homepage    = 'https://github.com/SunshineLibrary/distribute_tree'
+  s.license     = 'MIT'
+
+  s.files         = `git ls-files`.split("\n")
+  s.test_files    = `git ls-files -- test/{functional,unit}/*`.split("\n")
+  s.require_paths = ["lib"]
+
+  s.add_dependency "rails", ">= 3.2"
+  s.add_dependency 'haml-rails'
+  s.add_dependency "resque"
+  s.add_dependency "mongoid"
+  s.add_dependency "mongoid_uuid_generator"
+
+  s.add_development_dependency 'pry-debugger'
+  s.add_development_dependency 'guard-test'
+  s.add_development_dependency 'mongoid-rspec'
+  s.add_development_dependency 'capybara'
+  s.add_development_dependency 'factory_girl_rails'
+  s.add_development_dependency 'database_cleaner'
+
+  s.files = `git ls-files`.split("\n")
+end

data/lib/distribute_tree.rb

@@ -0,0 +1,104 @@
+# encoding: UTF-8
+
+require 'mongoid'
+require 'resque'
+
+module ::Mongoid
+  module DistributeTree
+    extend ActiveSupport::Concern
+    mattr_accessor :default_queue, :default_distribute_urls_proc, :is_allowed_model_proc
+    self.default_distribute_urls_proc = -> {}
+    self.is_allowed_model_proc = lambda {|model = nil| return false }
+
+    included do
+      @queue = Mongoid::DistributeTree.default_queue
+
+      # 配置和回调
+      cattr_accessor :distribute_children
+      self.distribute_children ||= []
+
+      # 是否该平台上分发
+      if Mongoid::DistributeTree.is_allowed_model_proc.call(self)
+        after_save     :distribute_without_children
+        after_destroy  :distribute_without_children
+      end if $IS_CLOUD_SERVER # 目前只在cloud上有
+    end
+
+    # 不递归 和 递归 两种
+    def distribute_without_children distribute_urls = nil; Utils.distribute self, distribute_urls, false end
+    def distribute_with_children    distribute_urls = nil; Utils.distribute self, distribute_urls, true  end
+
+    module Utils
+      def self.distribute item, distribute_urls, is_with_children
+        # embedded_in已经被父级同步
+        return false if item.class.relations.detect {|k, v| v.macro == :embedded_in }
+
+        # 分发到各URL
+        distribute_urls = Mongoid::DistributeTree.default_distribute_urls_proc.call if distribute_urls.nil?
+        distribute_urls = Array(distribute_urls).flatten.compact
+        distribute_urls.map do |_distribute_url|
+          Resque.enqueue item.class, item.uuid, _distribute_url, is_with_children
+          DistributeTreeStatus.insert item.class, item.uuid, _distribute_url
+        end
+      end
+    end
+
+    module ClassMethods
+      DeleteCallback = proc do |item_class, item_uuid, server_url|
+        DistributeTreeStatus.delete item_class, item_uuid, server_url
+      end
+
+      def perform _uuid, _distribute_url, is_with_children = false
+        klass = self
+        # 兼容 被删除 或者 软删除
+        item = (klass.respond_to?(:unscoped) ? klass.unscoped : klass).uuid(_uuid)
+        is_deleted = item.nil? || (item.respond_to?(:deleted?) && item.deleted?)
+
+        # sync data structure
+        payload = {
+          model_name: klass.name,
+          model: is_deleted ? {uuid: _uuid, delete: true} : item.as_json
+        }
+
+        # sync json
+        # RestClient.put "#{_distribute_url}/upload/warpgate", {:payload => payload}
+        # 会导致把app_versions解释为单个对象的Hash。
+        Rails.logger.info "[DistributeTree] begin sync #{klass}[#{item.uuid}] json at #{Time.now}"
+        RestClient.put "#{_distribute_url}/upload/warpgate.json", {:payload => payload}.to_json,  {:content_type => :json}
+        Rails.logger.info "[DistributeTree] end   sync #{klass}[#{item.uuid}] json at #{Time.now}"
+
+        # 不处理已经被删除的
+        (DeleteCallback.call(klass.name, _uuid, _distribute_url); return false) if is_deleted
+
+        paperclip_items = [item]
+        # 获取embeds_many里的含有paperclip对象，目前只支持一级
+        klass.relations.each do |k, v|
+          next if not v.macro == :embeds_many
+          paperclip_items += item.send(k).to_a
+        end
+        # 在paperclip文件对象选择上使用方法反射
+        paperclip_regexp = /_([a-z_]+)_post_process_callbacks/
+        paperclip_items.each do |paperclip_item|
+          next if not paperclip_item.methods.include?(:upload_path)
+          paperclip_method = paperclip_item.methods.detect {|m| m.match(paperclip_regexp) }.to_s.match(paperclip_regexp)[1]
+          file_path = paperclip_item.send(paperclip_method).path
+          next if not File.exists? file_path
+          Rails.logger.info "[DistributeTree] begin sync #{klass}[#{item.uuid}] file at #{Time.now}"
+          RestClient.put "#{_distribute_url}#{paperclip_item.upload_path}", :file => File.new(file_path, 'rb')
+          Rails.logger.info "[DistributeTree] end   sync #{klass}[#{item.uuid}] file at #{Time.now}"
+        end
+
+        # distribute children
+        item.distribute_children.each do |relation|
+          item.send(relation).to_a.each do |item2|
+            Resque.enqueue item2.class, item2.uuid, _distribute_url, is_with_children
+          end
+        end if is_with_children.to_s == 'true' # 兼容resque可能不能反序列化True/False
+
+        DeleteCallback.call(klass.name, _uuid, _distribute_url)
+      end
+
+    end
+
+  end
+end

data/lib/rails_engine.rb

@@ -0,0 +1,16 @@
+# encoding: UTF-8
+
+module DistributeTree
+
+  class Engine < Rails::Engine
+    initializer "distribute_tree.load_engine" do |app|
+      app.class.configure do
+        ['app/assets', 'app/controllers', 'app/views'].each do |path|
+          config.paths[path] ||= []
+          config.paths[path] += DistributeTree::Engine.paths[path].existent
+        end
+      end
+    end
+  end
+
+end

data/spec/dummy/.gitignore

@@ -0,0 +1,15 @@
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile ~/.gitignore_global
+
+# Ignore bundler config
+/.bundle
+
+# Ignore the default SQLite database.
+/db/*.sqlite3
+
+# Ignore all logfiles and tempfiles.
+/log/*.log
+/tmp

data/spec/dummy/Gemfile

@@ -0,0 +1,38 @@
+source 'https://rubygems.org'
+
+gem 'rails', '3.2.14'
+
+# Bundle edge Rails instead:
+# gem 'rails', :git => 'git://github.com/rails/rails.git'
+
+gem 'sqlite3'
+
+
+# Gems used only for assets and not required
+# in production environments by default.
+group :assets do
+  gem 'sass-rails',   '~> 3.2.3'
+  gem 'coffee-rails', '~> 3.2.1'
+
+  # See https://github.com/sstephenson/execjs#readme for more supported runtimes
+  # gem 'therubyracer', :platforms => :ruby
+
+  gem 'uglifier', '>= 1.0.3'
+end
+
+gem 'jquery-rails'
+
+# To use ActiveModel has_secure_password
+# gem 'bcrypt-ruby', '~> 3.0.0'
+
+# To use Jbuilder templates for JSON
+# gem 'jbuilder'
+
+# Use unicorn as the app server
+# gem 'unicorn'
+
+# Deploy with Capistrano
+# gem 'capistrano'
+
+# To use debugger
+# gem 'debugger'

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |   |   |-- images
+  |   |   |-- javascripts
+  |   |   `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.