modulate 0.0.1

data/app/controllers/modulate/application_controller.rb

@@ -0,0 +1,3 @@
+class Modulate::ApplicationController < ApplicationController
+
+end

data/app/models/modulate/document.rb

@@ -0,0 +1,39 @@
+class Modulate::Document < ActiveRecord::Base
+
+  attr_accessible :label, :public, :attachment
+
+  self.table_name = :modulate_documents
+
+  mount_uploader :attachment, Modulate::DocumentUploader
+
+  validates :attachable_id, :attachable_type, :bucket, :key, :filename, :content_type, :attachment, presence: true
+  validates :key, uniqueness: {scope: :bucket}
+
+  belongs_to :attachable, polymorphic: true
+
+  def key
+    return if filename.blank? || attachable.blank? || attachable.id.blank?
+    self[:key] ||= "#{attachable.id}-#{filename}"
+  end
+
+  def bucket
+    return if attachable_type.blank?
+    self[:bucket] ||= "#{Modulate.application_namespace}::#{attachable_type}"
+  end
+
+  def filename
+    return if attachment.file.blank?
+    self[:filename] ||= File.basename(attachment.file.file)
+  end
+
+  def content_type=(content_type)
+    return unless attachment.file
+    self[:content_type] = attachment.file.content_type = content_type
+  end
+
+  def content_type
+    return unless attachment.file
+    self[:content_type] ||= attachment.file.content_type
+  end
+
+end

data/app/uploaders/modulate/document_uploader.rb

@@ -0,0 +1,5 @@
+class Modulate::DocumentUploader < ::CarrierWave::Uploader::Riak
+  
+  delegate :key, :bucket, :filename, to: :model
+
+end

data/config/routes.rb

@@ -0,0 +1,5 @@
+Rails.application.routes.draw do
+  
+  resources :modulate_documents
+  
+end

data/db/migrate/20130320174022_add_modulate_document_table.rb

@@ -0,0 +1,27 @@
+class AddModulateDocumentTable < ActiveRecord::Migration
+  def up
+
+    create_table :modulate_documents do |z|
+      z.integer             :attached_by_id
+      z.integer             :attachable_id, null: false
+      z.string              :attachable_type, null: false
+      z.string              :attachment, null: false
+      z.string              :content_type, null: false
+      z.string              :filename, null: false
+      z.string              :bucket, null: false
+      z.string              :key, null: false
+      z.string              :label
+      z.boolean             :public, null: false, default: 0 
+
+      z.timestamps
+    end
+
+    add_index :modulate_documents, :key, unique: true
+
+  end
+
+  def down
+    drop_table :modulate_documents
+  end
+
+end

data/lib/generators/modulate/USAGE

@@ -0,0 +1,8 @@
+Description:
+    Explain the generator
+
+Example:
+    rails generate modulate Thing
+
+    This will create:
+        what/will/it/create

data/lib/generators/modulate/modulate_generator.rb

@@ -0,0 +1,33 @@
+class ModulateGenerator < Rails::Generators::Base
+  source_root File.expand_path('../templates', __FILE__)
+
+  desc "This generator will add document uploading functionality to a model you specify and create two views"
+
+  argument :model_name, type: :string, required: true
+
+  def edit_model
+    line = "class #{model_name.constantize} < ActiveRecord::Base"
+    gsub_file "app/models/#{model_name.underscore}.rb", /(#{Regexp.escape(line)})/mi do |match|
+      "#{match}\n  modulate\n"
+    end
+  end
+
+  def copy_view_files
+    template "_modulate_documents.html.haml", "app/views/#{model_name.underscore}s/_modulate_#{model_name.underscore}_documents.html.haml"
+    template "_modulate_attachments.html.haml", "app/views/#{model_name.underscore}s/_modulate_attachments.html.haml"
+  end
+
+  def copy_initializer
+    copy_file "_carrierwave.rb", "config/initializers/carrierwave.rb"
+  end
+
+  private
+
+  def gsub_file(relative_destination, regexp, *args, &block)
+    path = relative_destination
+    content = File.read(path).gsub(regexp, *args, &block)
+    File.open(path, 'wb') { |file| file.write(content) }
+  end 
+
+end
+

data/lib/generators/modulate/templates/_carrierwave.rb

@@ -0,0 +1,5 @@
+CarrierWave.configure do |config|
+  config.storage = :riak
+  config.riak_host = 'localhost'
+  config.riak_port = 8098
+end

data/lib/generators/modulate/templates/_modulate_attachments.html.haml

@@ -0,0 +1,11 @@
+= semantic_form_for @<%= model_name.underscore %> do |f|
+  = render "modulate_<%= model_name.underscore %>_documents", f: f
+
+  = f.inputs do
+    = f.semantic_fields_for :modulate_documents, @<%= model_name.underscore %>.modulate_documents.build do |d|
+      = d.input(:attachment, as: :file, label: 'Choose document to attach', required: true, 
+        input_html: {multiple: true}).sub('[attachment][]', '[attachment]').html_safe
+
+  = f.actions do
+    = f.action :submit, as: 'button', button_html: {class: 'btn btn-primary'}
+    = f.action :cancel, as: 'link', :label => "Cancel"

data/lib/generators/modulate/templates/_modulate_documents.html.haml

@@ -0,0 +1,31 @@
+%table.table.table-bordered.table-compressed
+  %thead
+    %tr
+      %th Label
+      %th File Name
+      %th Content Type
+      %th Uploaded At
+      %th Public
+      %th 
+      %th
+  %tbody
+    - if @<%= model_name.underscore %>.modulate_documents.any?
+      - @<%= model_name.underscore %>.modulate_documents.each do |document|
+        - next unless document.persisted?
+        = f.fields_for :modulate_documents, document do |d|
+          %tr
+            %td= d.text_field :label
+            %td= document.filename
+            %td= document.content_type
+            %td= I18n.l document.created_at
+            %td= d.check_box :public
+            %td
+              = link_to modulate_document_path(document), rel: 'tooltip', title: 'Download' do
+                %i.icon-download
+            %td
+              = link_to modulate_document_path(document), data: {method: :delete, confirm: "Are you sure?"}, rel: 'tooltip', title: 'Delete' do
+                %i.icon-remove-circle
+    - else
+      %tr
+        %td{colspan: 7}
+          .no-results There are no documents.

data/lib/modulate.rb

@@ -0,0 +1,20 @@
+require "modulate/engine"
+
+module Modulate
+
+  extend self
+
+  def application_namespace
+    Rails.application.class.name.split('::').first
+  end
+
+  def configuration
+    @configuration || configure
+  end
+
+  def configure
+    @configuration = Configuration.new
+    yield(@configuration) if block_given?
+    @configuration
+  end
+end

data/lib/modulate/configuration.rb

@@ -0,0 +1,10 @@
+module Modulate
+  class Configuration
+
+    attr_accessor :user_method
+
+    def initialize(method = nil)
+      @user_method = method
+    end
+  end
+end

data/lib/modulate/engine.rb

@@ -0,0 +1,21 @@
+require 'carrierwave/riak'
+require 'modulate/relation'
+require 'modulate/configuration'
+
+module Modulate
+
+  class Engine < ::Rails::Engine
+
+    config.to_prepare do
+      ActiveRecord::Base.extend Modulate::Relation
+    end
+
+    initializer "modulate.carrierwave.riak" do
+      CarrierWave.configure do |config|
+        config.storage = :riak
+      end
+    end
+
+  end
+
+end

data/lib/modulate/relation.rb

@@ -0,0 +1,10 @@
+module Modulate::Relation
+
+  def modulate(name=:modulate_documents, options={})
+    has_many name, {as: :attachable, class_name: "Modulate::Document"}.reverse_merge(options)
+    accepts_nested_attributes_for name 
+    attr_accessible :"#{name}_attributes"
+    attr_accessor :"#{Modulate.configuration.user_method}" unless Modulate.configuration.user_method == nil
+  end
+
+end

data/lib/modulate/version.rb

@@ -0,0 +1,3 @@
+module Modulate
+  VERSION = "0.0.1"
+end

data/lib/tasks/modulate_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :modulate do
+#   # Task goes here
+# end

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.