bacuview 1.5

data/AUTHORS

@@ -0,0 +1,2 @@
+The Bacuview application was written and is maintained by
+John Kodis, <john@kodis.org>

data/ChangeLog

@@ -0,0 +1,454 @@
+Wed, 2006 Nov 01, 15:24
+
+	* Added a job/last page, which shows the last successful full,
+	  differential, and incremental run of a job, with a count of the
+	  files and amount of data backed up.  This provides a way for
+	  people to get a quick status check on the backups of their
+	  workstations. 
+
+Thu, 2006 Aug 31, 14:25
+
+	* Modify the gruff support code to handle a failure to "require
+	  gruff", and move the pie chart generation to its own action to
+	  eliminate the need for a temporary file to hold the generated
+	  pie chart images.
+
+Wed, 2006 Aug 30, 16:29
+
+	* Added a bar graph to the Pool view, showing how the media are
+	  distributed among pools.
+
+Wed, 2006 Aug 23, 17:15
+
+	* Got the column sorting feature working even when using
+	  My-not-quite-SQL. 
+
+Fri, 2006 Aug 04, 13:54
+
+	* Added a two-column sort feature, and trimmed a few marginally
+	  useful columns from the index.rhtml pages.
+
+Wed, 2006 Aug 02, 09:48
+
+	* Take a guess at how many autochangers are in use, and adjust the
+	  display of the "slot" column accordingly.
+
+Mon, 2006 Jul 31, 15:39
+
+	* Eliminated the "rev" URL parameter, and tacked this information
+	  on the end of the sort parameter instead.
+
+Sun, 2006 May 14, 12:32
+
+	* Scaled the size of the client status images to 1 em square, and
+	  center them.
+
+Sat, 2006 Apr 15, 10:37
+
+	* Add a misc controller, currently supporting a fairly skeletal
+	  help and about page.
+
+Sat, 2006 Apr 15, 10:04
+
+	* Added a rake clean target, and a TODAY configuration variable,
+	  for test purposes.
+
+Fri, 2006 Apr 14, 15:11
+
+	* Added the Bacuview web site to the Bacuview application
+	  Subversion repository, deleted the doc/NEWS and doc/INSTALL
+	  files in preference to the HTML versions, and changed the
+	  installation instructions to recommend a released tar file
+	  rather than a direct subversion checkout.
+
+Tue, 2006 Apr 11, 14:16
+
+	* Changed the left nav bar to select jobs rather than clients;
+	  also dropped the anomalous jobs option, and leave job table
+	  capitalization alone.
+
+Sat, 2006 Mar 18, 08:36
+
+	* Released version 1.3.
+	
+	* Fix "rake dist" to simply pull from svn, clean up, and generate
+	  a tar file from there.
+
+Fri, 2006 Mar 10, 11:38
+
+	* Rename custom.yml file to bacuview.yml, and simplify the format.
+
+Mon, 2006 Mar 06, 07:18
+
+	* Add initial MySQL support: In environment.rb set STUDLY if using
+	  MySQL; In the models, add an if STUDLY section that redefines
+	  the table names and overrides the column accessors; in several
+	  views, use column accessor methods instead of instance
+	  variables.
+
+Sat, 2006 Mar 04, 08:06
+
+	* In job_helper, split level_name out into a seperate function to
+	  resolve a conflict: 'D' => 'Admin' or 'Diff'
+
+Thu, 2006 Mar 02, 15:28
+
+	* Added an "In Changer" column to the Media view.  Rails makes
+	  this type of change so easy it's almost embarrassing.  Almost.
+
+	* Added code to extract an OS_LIST from a query of client uname
+	  strings. 
+
+Mon, 2006 Feb 27, 18:12
+
+	* Released version 1.2.
+
+	* Fix a couple of problems with sorting by retention period in the
+	  media controller.
+
+	* Add rescue blocks around the config file ingest routines.  Also
+	  show how many files and client/hostname mappings were found when
+	  starting the application server.
+
+Sun, 2006 Feb 26, 18:40
+
+	* Fix calculation of media expiration time.
+
+Sun, 2006 Feb 26, 13:50
+
+	* Load customization parameters from a config/custom.yml at server
+	  startup time.  Initially this is used to get the path and glob
+	  to the bacula configuration files so that the client to hostname
+	  mapping can be extracted.
+
+Sat, 2006 Feb 25, 12:59
+
+	* Added media expiration and retention columns to the media view.
+	  Discovered what looks like two bugs in the process: Time <=>
+	  Fixnum doesn't work as specified in Ruby, and there seems to be
+	  a problem with using ORDER BY in conjunction with a JOIN in
+	  Rails.
+
+Mon, 2006 Feb 20, 11:00
+
+	* Eliminated a few more uses of 'style=' attributes in favor of
+	  'class=' attributes with the corresponding CSS class
+	  definitions.  Added an HTML 4.01 Transitional DOCTYPE to the
+	  standard layout.
+
+Sat, 2006 Feb 18, 11:14
+
+	* Add "session :disabled => true" to controllers/application.rb to
+	  avoid setting cookies so as to not upset the powers that be.
+
+Wed, 2006 Feb 15, 19:38
+
+	* Started work on a Job Specification page, an option-laden
+	  hodge-podge of job specification options.
+
+Wed, 2006 Feb 15, 10:42
+
+	* Released version 1.1, corresponding to Subversion revision 19.
+
+Fri, 2006 Feb 10, 18:57
+
+	* Added a nowrap style to the client, media, and pool index
+	  tables, and colorized the media volume status fields.
+
+Thu, 2006 Feb 09, 14:53
+
+	* Added a paragraph to the end of the client view noting that a
+	  file daemon status check can be performed by enabling
+	  Javascript, and a Javascript mechanism to hide this note if
+	  Javascript is already enabled.
+
+Wed, 2006 Feb 08, 18:13
+
+	* Got the server side client checking working.  Some cleanup is
+	  still required, but it all works.
+
+Mon, 2006 Feb 06, 18:19
+
+	* Added the AJAX support required to provide an on-demand client
+	  connectivity report from the client view.
+
+Sun, 2006 Feb 05, 18:43
+
+	* Changed the phrasing in the "No jobs" page.
+
+Sun, 2006 Feb 05, 10:43
+
+	* Define human_size_if_nz, and use it in job/index.rhtml to
+	  display the job rate and size as '-' if these values are zero,
+	  and as human sizes otherwise.
+
+Sun, 2006 Feb 05, 10:26
+
+	* Modify job_link to delete csort, msort, and psort options from
+	  jobs links in order to tidy up the URLs.
+
+Sat, 2006 Feb 04, 20:25
+
+	* Added a :joins clause to pull the pool name and type into each
+	  media record.  Updated media/index.rhtml to match.
+
+Sun, 2006 Jan 29, 10:30
+
+	* Released version 1.0 to RubyForge.
+
+Fri, 2006 Jan 20, 21:12
+
+	* Added the 'underline the selected sort field' feature to the
+          client, media, and pool index pages.
+
+Fri, 2006 Jan 20, 20:22
+
+	* Changed the select by date code to use the 'days.ago' routines.
+
+Wed, 2006 Jan 11, 23:10
+
+	* Before putting this into something resembling production
+          mode, I've created a 'bacuview' database user account to
+          provide read-only access to the tables used by the bacuview
+          application:
+
+	  # create user bacuview password 'bacuview';
+	  # grant select on job, jobmedia, client, media, pool to bacuview;
+
+	  Then add the magic to pg_hba.conf to allow the bacuview user
+	  to connect to the bacula database:
+
+	  host bacula bacuview 128.183.190.0/23 md5
+
+Tue, 2006 Jan 10, 19:13
+
+	* Spent the morning tweeking CSS rendering rules and adding a
+          message describing the exact type of jobs that have not been
+          found rather than simply displaying a blank page under these
+          circumstances.
+
+Sun, 2006 Jan 08, 10:56
+
+	* Prettied up the job media list.  Nulled out the id and
+          action settings in the job controllers so that these
+          wouldn't bleed through to other views.  Corrected the job
+          status strings to reflect what's shown in the bacula
+          database.
+
+Fri, 2006 Jan 06, 19:06
+
+	* Used find_by_sql to add an ugly list of the media used by
+          any one job to the job/show page.  I'll pretty it up later.
+
+Fri, 2006 Jan 06, 18:40
+
+	* Merged all of the munge_kay and munge_val methods into a
+          single pair of pretty_key and pretty_val methods in the
+          application_helper module.
+
+Thu, 2006 Jan 05, 20:38
+
+	* Tableized and munged the media/show page.  And the pool/show
+          page.  And the client/show page.  And finally, the job/show
+          page.
+
+Wed, 2006 Jan 04, 19:39
+
+	* Figured out that I had actually broken the link stickiness
+          yesterday and just hadn't noticed.  That drove me crazy when
+          I tried to figure out what it was about the job status
+          selection that caused this problem.
+
+Wed, 2006 Jan 04, 19:31
+
+	* Sometime in the near future, I hope to use this bit of SQL:
+	  select mediaid,volumename from media where mediaid in
+	  (select distinct mediaid from jobmedia where jobid = 381);
+
+Wed, 2006 Jan 04, 21:34
+
+	* Added support for the "list jobs with anomalous job
+          completion status" feature that Bobby requested.  It sort of
+          works, but the parameter list stickiness isn't quite right
+          yet.
+
+Tue, 2006 Jan 03, 19:39
+
+	* Massively simplified the page_link routines, and made the
+          corresponding changes to the .rhtml files for the various
+          views.
+
+Tue, 2006 Jan 03, 18:48
+
+	* Showed the application off to Bobby.  He seemed quite
+          impressed.
+
+Mon, 2006 Jan 02, 18:47
+
+	* Styled the header line and fixed the sorting for the client,
+          pool, and media views.
+
+Mon, 2006 Jan 02, 15:09
+
+	* Moved the CSS stuff into its own file.  All dozen lines of it.
+
+Mon, 2006 Jan 02, 14:16
+
+	* Added a time column showing how long a job took, to go with
+          the rate column.
+
+Mon, 2006 Jan 02, 13:22
+
+	* Alright, so it'll never really be done.  I've added a rate
+          column, and hooked up a sort function.  This took a bit of
+          work, since there's no rate column for the DB to sort on.
+
+Sun, 2006 Jan 01, 14:49
+
+	* Done.  Job selection by client, interval, sort field and
+          direction are all working.  The URL routing is set up to
+          start with a listing of the days jobs, and to minimize the
+          length of job URLs.  I'll make a few more cosmetic changes,
+          but the application itself is fully functional.
+
+Sat, 2005 Dec 31, 14:40
+
+	* I colorized the job status entries, and added a red Bacula
+	  Bat logo in the top left corner.  I couldn't resist.
+
+Sat, 2005 Dec 31, 13:24
+
+	* Almost done.  The job pages now accumulate the client,
+	  interval, and sort column specifications.  The sort
+	  direction still needs work, but I don't expect that to be a
+	  big deal.
+
+Fri, 2005 Dec 30, 17:13
+
+	* Alright, the client, pool, and media views and controllers
+          have been purged of their sort_by methods.
+
+Fri, 2005 Dec 30, 16:36
+
+	* Eliminated the use of the sort_by method in the Job class by
+          getting the database to handle the sorting.  I'll do the
+          same for the other views later.
+
+Thu, 2005 Dec 29, 20:34
+
+	* Eliminated the use of the scaffolding in the controllers.
+          This required the highly non-obvious inclusion of a method
+          "def index; list; end".  I also got rid of the use of the
+          debug statements that I was so fond of this morning, and
+          stole a simple three-line show.rhtml file instead.
+
+Thu, 2005 Dec 29, 19:47
+
+	* I killed the /new and /edit pages by defining empty
+          methods.  This causes a "Template is missing" error when an
+          attempt is made to get at these functions by hand-tuning the
+          URL, but it does make things less trivially hackable.  I
+          think that the real solution here is to drop the :scaffold
+          stuff that gets auto-generated, and do what I need manually.
+
+Thu, 2005 Dec 29, 19:37
+
+	* I wanted to get rid of the "Edit" and "Back" entries
+          provided by the scaffolding, so I created a set of
+          show.rhtml pages that each contain a line of the form:
+
+	      <%= debug(@job) %>
+
+	  This is enough to generate a fairly legible page.  Damn,
+	  this RoR stuff can be simple at times.
+
+Thu, 2005 Dec 29, 18:35
+
+	* Thanks to Chris Henley, I've discovered the magic of the
+          "white-space: nowrap" CSS tag.  My tables look just a little
+          less ugly as a result.
+
+Tue, 2005 Dec 27, 22:10
+
+	* Made good progress over the holiday weekend.  All of the
+          pages can now be sorted by column, although in only one
+          direction.  There's now a standard layout with a page
+          selector on the left and the actual content on the right.
+          It's quite ugly, but the information is all there.
+
+Wed, 2005 Dec 21, 19:07
+
+	* Alright, that's enough ugly table display pages.  Now the
+          fun job will be to pull these together through a menu of
+          some type.  Maybe tomorrow.
+
+Wed, 2005 Dec 21, 21:44
+
+	* Oops, I really meant to create a Media page.  I hope I can
+          get the pluralization right on this one.
+
+Wed, 2005 Dec 21, 20:22
+
+	* Let's set up a Pool page.  That ought to be enough different
+          pages that I can start setting up a menu to choose between
+          them. 
+
+	      $ ruby script/generate model Pool
+	      $ ruby script/generate controller Pool
+
+Wed, 2005 Dec 21, 20:05
+
+	* I got unstuck.  The type value is available as
+          job.attributes['type'].  Quirky, but I can live with it.
+          I've also added code to select based on client name.  It
+          seems like it would be better to use an SQL select rather
+          than screening rows that don't match, but the performance
+          doesn't suffer, so I'll worry about that later.
+
+Tue, 2005 Dec 20, 19:04
+
+	* I'm stuck.  The job page would have been done in a flash,
+          except that I can't get at the type column in the job table.
+          I've overridden the table name (def self.table_name() "job"
+          end) and get an error saying that "The STI mechanism failed
+          to locate the subclass: 'B'.", where the 'B' is the value of
+          the first type field.  I can get beyond this by adding
+          "Job.inheritance_column = 'ruby_type'" to the job model, but
+          then I'm unable to access the type field using the same
+          "<td><%= job.type %></td>" construct that works for all the
+          other fields.
+
+Tue, 2005 Dec 20, 18:22
+
+	* Amazing.  I got connected to the database and can generate a
+          web page with a list of all the clients, their uname and
+          retention periods.  It's rough but serviceable, and very
+          encouraging.
+
+	  Next, a Job page...
+
+	      $ ruby script/generate model Job
+	      $ ruby script/generate controller Job
+
+Tue, 2005 Dec 20, 17:55
+
+	* And so, the Bacurail project commences.  I've followed the
+	  recommendations on the http://rubyonrails.org/ web page and
+	  have downloaded a copy of the Ruby Gems package manager tar
+	  file, extracted the contents, then as root have run "ruby
+	  setup" and "gem install rails --include-dependencies" to get
+	  the basic rails installation set up.  Back as myself again,
+	  I used "rails bacurail" to create a basic rails directory
+	  structure, and plopped this into the doc directory.
+
+	  Given the rubygems-0.8.11.tgz file...
+	      $ tar xzf rubygems-0.8.11.tgz
+	      # cd rubygems-0.8.11
+	      # ruby setup.rb
+	      # gem install rails --include-dependencies
+	      # gem install postgres
+	      $ rails bacurail
+	      $ cd bacurail
+	      $ ruby script/generate controller Menu
+	      $ ruby script/generate controller Client
+	      $ ruby script/generate model Client

data/README.bacuview

@@ -0,0 +1,7 @@
+The Bacuview application provides a web-based view into the status of
+a Bacula backup system, as recorded in the Bacula database.  Bacuview
+has been developed and tested against both Postgres and MySQL databases.
+
+The Bacuview documentation is located in the public directory as a
+series of web pages, beginning with the Bacuview home page in
+public/home.html.

data/README.rails

@@ -0,0 +1,153 @@
+== Welcome to Rails
+
+Rails is a web-application and persistence framework that includes everything
+needed to create database-backed web-applications according to the
+Model-View-Control pattern of separation. 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. Run the WEBrick servlet: <tt>ruby script/server</tt> (run with --help for options)
+   ...or if you have lighttpd installed: <tt>ruby script/lighttpd</tt> (it's faster)
+2. Go to http://localhost:3000/ and get "Congratulations, you've put Ruby on Rails!"
+3. Follow the guidelines on the "Congratulations, you've put Ruby on Rails!" screen
+
+
+== Example for Apache conf
+
+  <VirtualHost *:80>
+    ServerName rails
+    DocumentRoot /path/application/public/
+    ErrorLog /path/application/log/server.log
+  
+    <Directory /path/application/public/>
+      Options ExecCGI FollowSymLinks
+      AllowOverride all
+      Allow from all
+      Order allow,deny
+    </Directory>
+  </VirtualHost>
+
+NOTE: Be sure that CGIs can be executed in that directory as well. So ExecCGI
+should be on and ".cgi" should respond. All requests from 127.0.0.1 go
+through CGI, so no Apache restart is necessary for changes. All other requests
+go through FCGI (or mod_ruby), which requires a restart to show changes.
+
+
+== Debugging Rails
+
+Have "tail -f" commands running on both the server.log, production.log, and
+test.log files. 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.
+
+
+== Breakpoints
+
+Breakpoint support is available through the script/breakpointer client. This
+means that you can break out of execution at any point in the code, investigate
+and change the model, AND then resume execution! Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find_all
+      breakpoint "Breaking out from the list"
+    end
+  end
+  
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the breakpointer window. Here you can do things like:
+
+Executing breakpoint "Breaking out from the list" at .../webrick_server.rb:16 in 'breakpoint'
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>, 
+       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
+  >> @posts.first.title = "hello from a breakpoint"
+  => "hello from a breakpoint"
+
+...and even better is that 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 press CTRL-D
+
+
+== Console
+
+You can interact with the domain model by starting the console through script/console. 
+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.
+Passing an argument will specify a different environment, like <tt>console production</tt>.
+
+
+== Description of contents
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/controllers
+  Holds controllers that should be named like weblog_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb.
+  Most models will descend from ActiveRecord::Base.
+  
+app/views
+  Holds the template files for the view that should be named like
+  weblog/index.rhtml for the WeblogController#index action. All views use eRuby
+  syntax. This directory can also be used to keep stylesheets, images, and so on
+  that can be symlinked to public.
+  
+app/helpers
+  Holds view helpers that should be named like weblog_helper.rb.
+
+config
+  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
+
+components
+  Self-contained mini-applications that can bundle together controllers, models, and views.
+
+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. Contains subdirectories for images, stylesheets,
+  and javascripts. Also contains the dispatchers and the default HTML files.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins subdirectory.
+  This directory is in the load path.