caboose-cms 0.0.2

data/db/migrate/20130421000000_drop_all_caboose.rb

@@ -0,0 +1,16 @@
+class DropAllCaboose < ActiveRecord::Migration  
+  def up
+    drop_table :users                if table_exists?('users')
+    drop_table :roles                if table_exists?('roles')
+    drop_table :permissions          if table_exists?('permissions')
+    drop_table :roles_users          if table_exists?('roles_users')
+    drop_table :permissions_roles    if table_exists?('permissions_roles')
+    drop_table :assets               if table_exists?('assets')
+    drop_table :pages                if table_exists?('pages')
+    drop_table :page_permissions     if table_exists?('page_permissions')
+  end
+  
+  def down
+    
+  end
+end

data/db/migrate/20130422000000_create_caboose.rb

@@ -0,0 +1,147 @@
+
+class CreateCaboose < ActiveRecord::Migration
+  
+  def up
+    create_tables
+    load_data
+  end
+  
+  def down
+    drop_table :users
+    drop_table :roles
+    drop_table :permissions
+    drop_table :roles_users
+    drop_table :permissions_roles
+  end
+  
+  #=============================================================================
+  
+  def create_tables
+
+    # User/Role/Permissions    
+  	create_table :users do |t|
+      t.string :first_name
+      t.string :last_name
+      t.string :username
+      t.string :email
+      t.string :password
+      t.string :password_reset_id
+      t.datetime :password_reset_sent
+      t.string :token     
+    end
+    create_table :roles do |t|
+      t.integer :parent_id
+      t.string :name
+      t.string :description
+    end
+    create_table :permissions do |t|
+      t.string :resource
+      t.string :action
+    end
+    
+    # Role membership
+    create_table :roles_users do |t|
+      t.references :role
+      t.references :user
+    end
+    add_index :roles_users, :role_id
+    add_index :roles_users, :user_id
+    
+    # Role permissions    
+    create_table :permissions_roles do |t|
+			t.references :role
+			t.references :permission
+		end
+		add_index :permissions_roles, :role_id
+		add_index :permissions_roles, :permission_id
+    
+    # Pages and Assets
+    create_table :assets do |t|
+      t.references  :page
+      t.references  :user
+      t.datetime    :date_uploaded
+      t.string      :name
+      t.string      :filename
+      t.string      :description
+      t.string      :extension      
+    end
+    create_table :pages do |t|
+      t.integer :parent_id
+      t.string  :title
+      t.string  :menu_title
+      t.text    :content
+      t.string  :slug
+      t.string  :alias
+      t.string  :uri
+      t.string  :redirect_url
+      t.boolean :hide, :default => false
+      t.integer :content_format, :default => Caboose::Page::CONTENT_FORMAT_HTML
+      t.text    :custom_css
+      t.text    :custom_js
+      t.string  :layout
+      t.integer :sort_order, :default => 0
+      t.boolean :custom_sort_children, :default => false
+      t.string  :seo_title, :limit => 70
+      t.string  :meta_description, :limit => 156
+      t.string  :meta_robots, :default => 'index, follow' # Multi-select options: none, noindex, nofollow, nosnippet, noodp, noarchive
+      t.string  :canonical_url
+      t.string  :fb_description, :limit => 156
+      t.string  :gp_description, :limit => 156
+    end
+    create_table :page_permissions do |t|
+      t.references  :role
+      t.references  :page
+      t.string      :action
+    end
+		
+  end
+  
+  #=============================================================================
+  
+  def load_data
+    
+    admin_user = Caboose::User.create(first_name: 'Admin', last_name: 'User', username: 'admin', email: 'william@nine.is')
+    admin_user.password = Digest::SHA1.hexdigest(Caboose::salt + 'caboose')
+    admin_user.save
+    
+    admin_role  = Caboose::Role.create(parent_id: -1, name: 'Admin')
+    elo_role    = Caboose::Role.create(parent_id: -1, name: 'Everyone Logged Out')
+    eli_role    = Caboose::Role.create(parent_id: elo_role.id, name: 'Everyone Logged In')
+    
+    elo_user = Caboose::User.create(first_name: 'John', last_name: 'Doe', username: 'elo', email: 'william@nine.is')
+    
+    admin_perm = Caboose::Permission.create(resource: 'all', action: 'all')
+    Caboose::Permission.create(resource: 'users'	      , action: 'view')
+    Caboose::Permission.create(resource: 'users'	      , action: 'edit')
+    Caboose::Permission.create(resource: 'users'	      , action: 'delete')
+    Caboose::Permission.create(resource: 'users'	      , action: 'add')
+    Caboose::Permission.create(resource: 'roles'	      , action: 'view')
+    Caboose::Permission.create(resource: 'roles'	      , action: 'edit')
+    Caboose::Permission.create(resource: 'roles'	      , action: 'delete')
+    Caboose::Permission.create(resource: 'roles'	      , action: 'add')
+    Caboose::Permission.create(resource: 'permissions'	, action: 'view')
+    Caboose::Permission.create(resource: 'permissions'	, action: 'edit')
+    Caboose::Permission.create(resource: 'permissions'	, action: 'delete')
+    Caboose::Permission.create(resource: 'permissions'	, action: 'add')
+
+    # Add the admin user to the admin role
+    admin_user.roles.push(admin_role)
+    admin_user.save
+    
+    # Add the elo to the elo role
+    elo_user.roles.push(elo_role)
+    elo_user.save
+
+    # Add the all/all permission to the admin role
+    admin_role.permissions.push(admin_perm)
+    admin_role.save
+    
+    # Create the home page
+    home_page  = Caboose::Page.create(title: 'Home'  , parent_id: -1, hide: 0, layout: 'home'   , uri: '')
+    admin_page = Caboose::Page.create(title: 'Admin' , parent_id: home_page.id, hide: 0, layout: 'admin', alias: 'admin', slug: 'admin', uri: 'admin')
+    login_page = Caboose::Page.create(title: 'Login' , parent_id: home_page.id, hide: 0, layout: 'login', alias: 'login', slug: 'login', uri: 'login')
+    Caboose::PagePermission.create(role_id: elo_role.id, page_id: home_page.id, action: 'view') 
+    Caboose::PagePermission.create(role_id: elo_role.id, page_id: login_page.id, action: 'view')
+    
+  end
+end

data/lib/caboose.rb

@@ -0,0 +1,26 @@
+require "caboose/engine"
+
+module Caboose
+
+  mattr_accessor :salt
+  @@salt = "This needs to be changed pronto."
+
+  mattr_accessor :assets_path
+  @@assets_path = "assets"
+  
+  mattr_accessor :plugins
+  @@plugins = []
+
+  # Any paths to modeljs javascript files  
+  mattr_accessor :modeljs_js_files
+  @@modeljs_js_files = []
+  
+  mattr_accessor :modeljs_js_paths
+  @@modeljs_js_paths = []
+  
+  # Any modeljs stylesheets
+  mattr_accessor :modeljs_css_files
+  @@modeljs_css_files = []
+
+end
+

data/lib/caboose/engine.rb

@@ -0,0 +1,24 @@
+module Caboose
+  
+  def Caboose.log(message, title = nil)
+    Rails.logger.debug("\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>")
+    Rails.logger.debug(title.to_s) unless title.nil?
+    Rails.logger.debug(message)
+    Rails.logger.debug(">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\n")    
+  end
+  
+  def Caboose.plugin_hook(tag, args = nil)
+    Caboose.plugins.each do |mod|
+      func = "#{tag}_hook"  
+      if (mod.constantize.respond_to?(func))
+        args = mod.constantize.send(func.to_sym, args)
+      end
+      #args = mod.send(func.to_sym, args)
+    end
+    return args
+  end
+  
+  class Engine < ::Rails::Engine
+    isolate_namespace Caboose    
+  end
+end

data/lib/caboose/version.rb

@@ -0,0 +1,3 @@
+module Caboose
+  VERSION = "0.0.2"
+end

data/lib/tasks/caboose_tasks.rake

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

data/test/caboose_test.rb

@@ -0,0 +1,7 @@
+require 'test_helper'
+
+class CabooseTest < ActiveSupport::TestCase
+  test "truth" do
+    assert_kind_of Module, Caboose
+  end
+end

data/test/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.