RubyGems - pgq_web - Versions diffs - 0.0.1 - Mend

pgq_web 0.0.1

Files changed (117) hide show

data/app/helpers/pgq_web/pgq_helper.rb ADDED Viewed

@@ -0,0 +1,22 @@
+module PgqWeb::PgqHelper
+  def class_menu(act)
+    act == params[:action] ? 'active' : ''
+  end
+  def status_span(status = :ok)
+    case status
+    when :ok then content_tag(:span, 'ok', :class => "label label-success")
+    when :warn then content_tag(:span, 'warn', :class => "label label-warning")
+    when :error then content_tag(:span, 'error', :class => "label label-important")
+    when :stopped then content_tag(:span, 'stopped', :class => "label")
+    else
+      content_tag(:span, 'ok', :class => "label label-success")
+    end
+  end
+  def human_time(str_time)
+    Time.parse(str_time).strftime("%d.%m.%Y %H:%M:%S") rescue '-'
+  end
+end

data/app/models/pgq_web/watcher.rb ADDED Viewed

@@ -0,0 +1,4 @@
+module PgqWeb
+  class Watcher
+  end
+end

data/app/views/layouts/pgq_web/application.html.erb ADDED Viewed

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>PgqWeb</title>
+  <%= stylesheet_link_tag    "pgq_web/application", :media => "all" %>
+  <%= javascript_include_tag "pgq_web/application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+<%= yield %>
+</body>
+</html>

data/app/views/layouts/pgq_web/pgq.html.erb ADDED Viewed

@@ -0,0 +1,18 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>PgQ Info</title>
+  <%= stylesheet_link_tag    "pgq_web/application", :media => "all" %>
+  <%= javascript_include_tag "pgq_web/application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+<%= render :partial => "pgq_web/pgq/menu" %>
+<div class="container">
+  <%= yield %>
+</div>
+</body>
+</html>

data/app/views/pgq_web/pgq/_error.haml ADDED Viewed

@@ -0,0 +1,21 @@
+- error['ev_failed_reason'] = Pgq::Consumer.coder.load(error['ev_failed_reason'])
+- error['ev_data'] = Pgq::Consumer.coder.load(error['ev_data'])
+- reason = error['ev_failed_reason']
+%div{:id => "ev_#{error['ev_id']}"}
+  %div
+    = error['ev_id']
+    (#{human_time(error['ev_failed_time'])})
+    = link_to_function "[details]", "$('##{"ev_#{error['ev_id']}_det"}').toggle()"
+    = link_to "[retry]", {:action => "retry", :queue_name => @queue_name, :consumer_name => @consumer_name, :ev_id => error['ev_id'], :db_index => params[:db_index]}, :remote => true, :title => "Retry failed event"
+    = link_to "[delete]", {:action => 'delete', :queue_name => @queue_name, :consumer_name => @consumer_name, :ev_id => error['ev_id'], :db_index => params[:db_index]}, :confirm => "Are you sure, delete event?", :title => "Delete failed event", :remote => true
+  %div
+    %span{:style => "padding-top:0px; padding-bottom:0px", :class => "alert alert-error"}
+      = ":#{error['ev_type']} => (#{reason[:class]}) #{reason[:message]}"
+  %div{:id => "ev_#{error['ev_id']}_det", :class => "", :style => "margin-left: 20px; display: none"}
+    %div InsertAt: #{human_time error['ev_time']}
+    %div FailedAt: #{human_time error['ev_failed_time']}
+    %div EventType: #{error['ev_type']}
+    %div Data: #{error['ev_data'].join(",")}
+    %div Backtrace:
+    %div{:style => "margin-left: 20px"}= reason[:backtrace].join("<br>").html_safe

data/app/views/pgq_web/pgq/_menu.haml ADDED Viewed

@@ -0,0 +1,15 @@
+%div{:class => "navbar navbar-fixed-top"}
+  %div{:class => "navbar-inner"}
+    %div{:class => "container"}
+      = link_to "PgQ Info", {:action => :index}, :class => "brand"
+      %ul{:class => "nav"}
+        %li{:class => class_menu('index')}= link_to 'Queues', :action => :index
+        %li{:class => class_menu('errors')}= link_to 'Errors', :action => :errors
+        - if params[:action] == 'errors_list'
+          %li{:class => "active"}= link_to 'Errors List', '#'
+        - if params[:action] == 'pending_list'
+          %li{:class => "active"}= link_to 'Pending List', '#'
+%br
+%br
+%br

data/app/views/pgq_web/pgq/_pags.haml ADDED Viewed

@@ -0,0 +1,3 @@
+%span On page:
+- [10, 30, 100, 1000].each do |pp|
+  = link_to_unless_current pp, params.merge(:per_page => pp)

data/app/views/pgq_web/pgq/_pending_events_res.haml ADDED Viewed

@@ -0,0 +1,4 @@
+- if @res == '-'
+  %i{:class => "icon-ban-circle"}
+- else
+  = link_to @res.to_s, {:action => "pending_list", :queue_name => params[:queue_name], :db_index => params[:db_index], :last_event => @last_event.to_i}

data/app/views/pgq_web/pgq/delete.js.erb ADDED Viewed

	@@ -0,0 +1 @@
1	+ $('#<%="ev_#{params['ev_id']}"%>').html('<%= @res %>');

data/app/views/pgq_web/pgq/errors.haml ADDED Viewed

@@ -0,0 +1,21 @@
+%h3 Pgq Errors (#{@info.size})
+%table{:class => "table table-bordered", :style => "width:600px"}
+  %thead
+    %tr
+      - @keys.each do |column|
+        %td{:align => 'center'}= @keys_names[column]
+  %tbody
+    - @info.each do |row|
+      %tr
+        - @keys.each do |key|
+          %td{:align => 'center'}
+            - case key
+            - when 'errors_count'
+              = link_to row[key], {:action => "errors_list", :queue_name => row['queue_name'], :consumer_name => row['consumer_name'], :db_index => row['db_index']}, :title => "Go to details"
+            - when 'actions'
+              %span= link_to '<i class="icon-repeat"></i>'.html_safe, {:action => "retry_all", :consumer_name => row['consumer_name'], :queue_name => row['queue_name'], :db_index => row['db_index']}, :title => "Retry 5000 failed events"
+              %span= link_to '<i class="icon-trash"></i>'.html_safe, {:action => 'delete_all', :consumer_name => row['consumer_name'], :queue_name => row['queue_name'], :db_index => row['db_index']}, :confirm => "Are you sure, delete events?", :title => "Delete 5000 failed events"
+            - else
+              = row[key]

data/app/views/pgq_web/pgq/errors_list.haml ADDED Viewed

@@ -0,0 +1,13 @@
+%h3 #{params[:queue_name]} errors(#{@errors_count})
+= render :partial => "pags"
+= will_paginate @errors
+%table{:class => "table"}
+  - @errors.each do |error|
+    %tr
+      %td
+        = render :partial => 'error', :object => error
+= will_paginate @errors

data/app/views/pgq_web/pgq/index.haml ADDED Viewed

@@ -0,0 +1,22 @@
+- @info_groups.each do |((host, db), info_group)|
+  %h3 #{db}@#{host} (#{info_group.size})
+  %br
+  %table{:class => "table table-bordered"}
+    %thead
+      %tr
+        - @keys.each do |column|
+          %td{:align => 'center'}= @keys_names[column]
+    %tbody
+      - info_group.each do |row|
+        %tr
+          - @keys.each do |key|
+            %td{:align => "center"}
+              - if key == 'pending_events'
+                %span= link_to '<i class="icon-time"></i>'.html_safe, {:action => "pending_events_count", :queue_name => row['queue_name'], :db_index => row['db_index']}, {:remote => true, :title => "Load pending events count for queue", :onclick => "$('##{"pe_ev" + row['queue_name']}').html('')"}
+                %span{:id => "pe_ev" + row['queue_name']}
+              - elsif key == 'status'
+                = status_span(row['status'])
+              - else
+                = row[key]

data/app/views/pgq_web/pgq/pending_events_count.js.erb ADDED Viewed

	@@ -0,0 +1 @@
1	+ $('#<%="pe_ev" + params['queue_name']%>').html('<%= escape_javascript render(:partial => "pending_events_res") %>');

data/app/views/pgq_web/pgq/pending_list.haml ADDED Viewed

@@ -0,0 +1,20 @@
+%h3 #{params[:queue_name]} pending (#{@pending_count})
+= render :partial => "pags"
+= will_paginate @pending
+%table{:class => "table table-bordered", :style => "font-size: 8pt;"}
+  %tr
+    %td{:width => "10%"} EvId
+    %td{:width => "15%"} Insert At
+    %td{:width => "20%"} Event Type
+    %td Data
+  - @pending.each do |event|
+    %tr
+      %td= event['ev_id']
+      %td= Time.parse(event['ev_time']).strftime("%d.%m.%Y %H:%M:%S") rescue '-'
+      %td= event['ev_type']
+      %td= Pgq::Consumer.coder.load(event['ev_data']).join(",") rescue '-'
+= will_paginate @pending

data/app/views/pgq_web/pgq/retry.js.erb ADDED Viewed

	@@ -0,0 +1 @@
1	+ $('#<%="ev_#{params['ev_id']}"%>').html('<%= @res %>');

data/config/initializers/databases.rb ADDED Viewed

@@ -0,0 +1,8 @@
+class PgqWeb::Watcher
+  class << self
+    attr_accessor :databases
+  end
+  self.databases = [ ActiveRecord::Base ]
+end

data/config/initializers/will_paginate_init.rb ADDED Viewed

@@ -0,0 +1,32 @@
+require 'will_paginate/view_helpers/link_renderer'
+require 'will_paginate/view_helpers/action_view'
+module WillPaginate
+  module ActionView
+    def will_paginate(collection = nil, options = {})
+      options[:renderer] ||= BootstrapLinkRenderer
+      super.try :html_safe
+    end
+    class BootstrapLinkRenderer < LinkRenderer
+      protected
+      def html_container(html)
+        tag :div, tag(:ul, html), container_attributes
+      end
+      def page_number(page)
+        tag :li, link(page, page, :rel => rel_value(page)), :class => ('active' if page == current_page)
+      end
+      def previous_or_next_page(page, text, classname)
+        tag :li, link(text, page || '#'), :class => [classname[0..3], classname, ('disabled' unless page)].join(' ')
+      end
+      def gap
+        tag :li, link(super, '#'), :class => 'disabled'
+      end
+    end
+  end
+end

data/config/routes.rb ADDED Viewed

@@ -0,0 +1,4 @@
+PgqWeb::Engine.routes.draw do
+  match '/' => 'pgq#index'
+  match '/:action(/:id)' => "pgq#"
+end

data/lib/pgq_web/engine.rb ADDED Viewed

@@ -0,0 +1,5 @@
+module PgqWeb
+  class Engine < ::Rails::Engine
+    isolate_namespace PgqWeb
+  end
+end

data/lib/pgq_web/version.rb ADDED Viewed

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

data/lib/pgq_web.rb ADDED Viewed

@@ -0,0 +1,4 @@
+require "pgq_web/engine"
+module PgqWeb
+end

data/lib/tasks/pgq_web_tasks.rake ADDED Viewed

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

data/test/dummy/README.rdoc ADDED Viewed

@@ -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.

data/test/dummy/Rakefile ADDED Viewed

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+require File.expand_path('../config/application', __FILE__)
+Dummy::Application.load_tasks

data/test/dummy/app/assets/javascripts/application.js ADDED Viewed

@@ -0,0 +1,15 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require_tree .

data/test/dummy/app/assets/stylesheets/application.css ADDED Viewed

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+*/

data/test/dummy/app/controllers/application_controller.rb ADDED Viewed

@@ -0,0 +1,3 @@
+class ApplicationController < ActionController::Base
+  protect_from_forgery
+end

data/test/dummy/app/helpers/application_helper.rb ADDED Viewed

	@@ -0,0 +1,2 @@
1	+ module ApplicationHelper
2	+ end

data/test/dummy/app/models/base2.rb ADDED Viewed

@@ -0,0 +1,4 @@
+class Base2 < ActiveRecord::Base
+  self.abstract_class = true
+  establish_connection "#{Rails.env || 'development'}2"
+end

data/test/dummy/app/models/pgq/pgq_cleanup.rb ADDED Viewed

@@ -0,0 +1,10 @@
+class PgqCleanup < Pgq::Consumer
+  # to insert event: PgqCleanup.my_event(1, 2, 3)
+  # async execute
+  def my_event(a, b, c)
+    logger.info "async call my_event with #{[a, b, c].inspect}"
+  end
+end

data/test/dummy/app/models/pgq/pgq_history.rb ADDED Viewed

@@ -0,0 +1,10 @@
+class PgqHistory < Pgq::Consumer
+  # to insert event: PgqHistory.my_event(1, 2, 3)
+  # async execute
+  def my_event(a, b, c)
+    logger.info "async call my_event with #{[a, b, c].inspect}"
+  end
+end

data/test/dummy/app/models/pgq/pgq_issues.rb ADDED Viewed

@@ -0,0 +1,11 @@
+class PgqIssues < Consumer2
+  # to insert event: PgqIssue.my_event(1, 2, 3)
+  # async execute
+  def my_event(a, b, c)
+    sleep 0.2
+    logger.info "async call my_event with #{[a, b, c].inspect}"
+  end
+end

data/test/dummy/app/models/pgq/pgq_pack_files.rb ADDED Viewed

@@ -0,0 +1,10 @@
+class PgqPackFile < Pgq::Consumer
+  # to insert event: PgqPackFile.my_event(1, 2, 3)
+  # async execute
+  def my_event(a, b, c)
+    logger.info "async call my_event with #{[a, b, c].inspect}"
+  end
+end

data/test/dummy/app/models/pgq/pgq_places.rb ADDED Viewed

@@ -0,0 +1,10 @@
+class PgqPlaces < Pgq::Consumer
+  # to insert event: PgqPlaces.my_event(1, 2, 3)
+  # async execute
+  def my_event(a, b, c)
+    logger.info "async call my_event with #{[a, b, c].inspect}"
+  end
+end