jobbr 1.0.1

data/app/views/layouts/jobbr/application.html.haml

@@ -0,0 +1,20 @@
+!!! XML
+!!!
+%html{ :xmlns => 'http://www.w3.org/1999/xhtml'  }
+  %head
+    %title JobbR
+
+    = csrf_meta_tags
+
+    = stylesheet_link_tag    'jobbr/application'
+    = javascript_include_tag 'jobbr/application'
+
+  %body
+    .navbar
+      .navbar-inner
+        %a.brand= t('.title')
+        %button.btn#auto-refresh{type: 'button', 'data-toggle' => 'button'}
+          %i.icon-refresh
+          = t('.auto_refresh')
+    #main.container
+      = yield

data/config/locales/jobbr.en.yml

@@ -0,0 +1,39 @@
+en:
+
+  layouts:
+    jobbr:
+      application:
+        title: JobbR
+        auto_refresh: Auto-refresh
+
+  jobbr:
+
+    jobs:
+
+      index:
+        title: Job list
+        scheduled_jobs: Scheduled Jobs
+        delayed_jobs: Delayed Jobs
+
+      job_list:
+        status: Status
+        job_name: Name
+        last_run: Last runned at
+        average_run_time: Average run time
+        see_all_runs: See all runs
+        see_last_run: See last run
+
+      show:
+        status: Status
+        last_run: Last run
+        last_run_logs: Last run logs
+        duration: Duration
+        scheduling: "Scheduled every <strong>%{scheduling}</strong>"
+        average_run_time: "Average duration: <strong>%{run_time}</strong>"
+        see_run: See details for this run
+
+    runs:
+      show:
+        run_time: "Run time: %{run_time}"
+        previous_run: "Previous run"
+        next_run: "Next run"

data/config/routes.rb

@@ -0,0 +1,11 @@
+Jobbr::Engine.routes.draw do
+
+  root to: 'jobs#index'
+
+  resources :jobs do
+    resources :runs
+  end
+
+  resources :delayed_jobs
+
+end

data/jobbr.gemspec

@@ -0,0 +1,25 @@
+$:.push File.expand_path("../lib", __FILE__)
+
+require "jobbr/version"
+
+Gem::Specification.new do |s|
+  s.name        = "jobbr"
+  s.version     = Jobbr::VERSION
+  s.authors     = ["Christian Blavier"]
+  s.email       = ["cblavier@gmail.com"]
+  s.homepage    = "https://github.com/cblavier/jobbr"
+  s.summary     = "Rails supervision UI for your Cron jobs and your Delayed Jobs."
+  s.description = "Jobbr provideds a convenient framework and UI to make your Cron jobs and Scheduled Jobs more manageable."
+
+  s.files         = `git ls-files`.split("\n")
+  s.test_files    = `git ls-files -- spec/*`.split("\n")
+  s.require_paths = ["lib"]
+
+  s.add_dependency "rails", "~> 3.2"
+  s.add_dependency "mongoid", "~> 3.0"
+  s.add_dependency "whenever"
+  s.add_dependency "chronic_duration"
+
+  s.add_development_dependency 'sqlite3'
+  s.add_development_dependency 'combustion', '~> 0.3.1'
+end

data/lib/jobbr.rb

@@ -0,0 +1,4 @@
+require "jobbr/engine"
+
+module Jobbr
+end

data/lib/jobbr/engine.rb

@@ -0,0 +1,7 @@
+module Jobbr
+  class Engine < ::Rails::Engine
+
+    isolate_namespace Jobbr
+
+  end
+end

data/lib/jobbr/logger.rb

@@ -0,0 +1,55 @@
+module Jobbr
+
+  class Logger
+
+    FLUSH_DELAY = 5
+
+    attr_accessor :run, :last_flush_at, :wrapped_logger, :level
+
+    def initialize(logger, run)
+      self.wrapped_logger = logger
+      self.run = run
+      self.level = 0
+    end
+
+    def debug(message)
+      wrapped_logger.debug(message)
+      write_message(:debug, message)
+    end
+
+    def info(message)
+      wrapped_logger.info(message)
+      write_message(:info, message)
+    end
+
+    def warn(message)
+      wrapped_logger.warn(message)
+      write_message(:warn, message)
+    end
+
+    def error(message)
+      wrapped_logger.error(message)
+      write_message(:error, message)
+    end
+
+    def fatal(message)
+      wrapped_logger.error(message)
+      write_message(:fatal, message)
+    end
+
+    protected
+
+    def write_message(kind, message)
+      if message.is_a? Array
+        message = message.join('<br/>')
+      end
+      run.log_messages << Jobbr::LogMessage.new(kind: kind, message: message, date: Time.now)
+      if last_flush_at.nil? || (last_flush_at + FLUSH_DELAY.seconds < Time.now)
+        run.save!
+        self.last_flush_at = Time.now
+      end
+    end
+
+  end
+
+end

data/lib/jobbr/mongoid.rb

@@ -0,0 +1,54 @@
+module Jobbr
+
+  module Mongoid
+
+    include ::Mongoid
+
+    extend self
+
+    # Return all Mongoid models.
+    # You can also pass a parent class to get all Mongoid childrens
+    #
+    # @example Return *all* models.
+    #   Rails::Mongoid.models
+    #
+    # @example Return Job children models.
+    #   Rails::Mongoid.models(Job)
+    #
+    # @param [ Class ] parent The parent model class.
+    #
+    # @return [ Array<Class> ] The models.
+    #
+    def models(parent = nil)
+      model_paths = Dir["#{Rails.root}/app/models/**/*.rb"]
+      sanitized_model_paths = model_paths.map { |path| path.gsub(/.*\/app\/models\//, '').gsub('.rb', '') }
+      model_constants = sanitized_model_paths.map do |path|
+        path.split('/').map { |token| token.camelize }.join('::').constantize
+      end
+      model_constants = model_constants.select { |constant| constant.include?(Mongoid::Document) }
+
+      if parent
+        model_constants.select { |model| superclasses(model).include?(parent) }
+      else
+        model_constants
+      end
+    end
+
+    # Return all superclasses for a given class.
+    #
+    # @param [ Class ] parent The class you want to get superclasses from.
+    #
+    # @return [ Array<Class> ] The superclasses.
+    #
+    def superclasses(klass)
+      super_classes = []
+      while klass != Object
+        klass = klass.superclass
+        super_classes << klass
+      end
+      super_classes
+    end
+
+  end
+
+end

data/lib/jobbr/version.rb

@@ -0,0 +1,3 @@
+module Jobbr
+  VERSION = "1.0.1"
+end

data/lib/jobbr/whenever.rb

@@ -0,0 +1,24 @@
+require "jobbr/mongoid"
+
+module Jobbr
+
+  module Whenever
+
+    extend self
+
+    #
+    # Generates crontab for each scheduled Job using Whenever DSL.
+    #
+    def schedule_jobs(job_list)
+      Jobbr::Mongoid.models(Jobbr::ScheduledJob).each do |job|
+        if job.every
+          job_list.every job.every[0], job.every[1] do
+            job_list.rake job.task_name(true)
+          end
+        end
+      end
+    end
+
+  end
+
+end

data/lib/tasks/jobbr_tasks.rake

@@ -0,0 +1,14 @@
+models_root = File.expand_path(File.join(File.dirname(__FILE__), '..', '..', 'app', 'models'))
+require File.join(models_root, 'jobbr', 'standalone_tasks')
+
+namespace :jobbr do
+
+  Jobbr::StandaloneTasks.all(:scheduled_job).each do |info|
+    # dynamically create a rake task for each individual Jobbr::ScheduledJob
+    desc info[:desc]
+    task info[:name] => :environment do
+      info[:dependencies].each { |lib| load lib }
+      info[:klass_name].constantize.run
+    end
+  end
+end

data/script/rails

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby
+# This command will automatically be run when you run "rails" with Rails 3 gems installed from the root of your application.
+
+ENGINE_ROOT = File.expand_path('../..', __FILE__)
+ENGINE_PATH = File.expand_path('../../lib/jobbr/engine', __FILE__)
+
+require 'rails/all'
+require 'rails/engine/commands'

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
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- 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.