OOD App Kit

The ood_appkit gem is a package of utility functions and engines for applications running on the Open OnDemand platform.

Functionality includes:

• Rake tasks
• URL handlers for OOD System applciations
• Rack middleware for handling files under a configured dataroot
• A wiki static page engine
• Override Bootstrap Variables
• A markdown handler
• Custom Log Formatting
• Branding Features
• Information on Configured Clusters

To use, add this line to your application's Gemfile:

gem 'ood_appkit'

And then execute:

bundle install

Running this rake task

bin/rake ood_appkit:reset

will clear the Rails cache and update the timestamp on the tmp/restart.txt file that is used by Passenger to decide whether to restart the application.

This is the URL used to access publicly available assets provided by the OOD infrastructure, e.g., the favicon.ico.

<%= favicon_link_tag nil, href: OodAppkit.public.url.join('favicon.ico') %>

Note: We used nil here as the source otherwise Rails will try to prepend the RAILS_RELATIVE_URL_ROOT to it. We explicitly define the link using href: instead.

You can change the options using environment variables:

OOD_PUBLIC_URL='/public'
OOD_PUBLIC_TITLE='Public Assets'

Or by modifying the configuration in an initializer:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  # Defaults
  config.public = OodAppkit::PublicUrl.new title: 'Public Assets', base_url: '/public'
end

<%= link_to OodAppkit.dashboard.title, OodAppkit.dashboard.url.to_s %>

You can change the options using environment variables:

OOD_DASHBOARD_URL='/pun/sys/dashboard'
OOD_DASHBOARD_TITLE='Open OnDemand'

Or by modifying the configuration in an initializer:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  # Defaults
  config.dashboard = OodAppkit::Urls::Dashboard.new title: 'Open OnDemand', base_url: '/pun/sys/dashboard'
end

<%# Link to the Files app %>
<%= link_to OodAppkit.files.title, OodAppkit.files.url.to_s %>

<%# Link to open files app to specified directory %>
<%= link_to "/path/to/file", OodAppkit.files.url(path: "/path/to/file").to_s %>
<%= link_to "/path/to/file", OodAppkit.files.url(path: Pathname.new("/path/to/file")).to_s %>

<%# Link to retrieve API info for given file %>
<%= link_to "/path/to/file", OodAppkit.files.api(path: "/path/to/file").to_s %>

You can change the options using environment variables:

OOD_FILES_URL='/pun/sys/files'
OOD_FILES_TITLE='Files'

Or by modifying the configuration in an initializer:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  # Defaults
  config.files = OodAppkit::Urls::Files.new title: 'Files', base_url: '/pun/sys/files'
end

<%# Link to the Editor app %>
<%= link_to OodAppkit.editor.title, OodAppkit.editor.url.to_s %>

<%# Link to open file editor app to edit specific file %>
<%= link_to "Edit /path/to/file", OodAppkit.editor.edit(path: "/path/to/file").to_s %>
<%= link_to "Edit /path/to/file", OodAppkit.editor.edit(path: Pathname.new("/path/to/file")).to_s %>

You can change the options using environment variables:

OOD_EDITOR_URL='/pun/sys/file-editor'
OOD_EDITOR_TITLE='EDITOR'

Or by modifying the configuration in an initializer:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  # Defaults
  config.editor = OodAppkit::Urls::Editor.new title: 'Editor', base_url: '/pun/sys/file-editor'
end

<%# Link to the Shell app %>
<%= link_to OodAppkit.shell.title, OodAppkit.shell.url.to_s %>

<%# Link to launch Shell app for specified host %>
<%= link_to "Ruby Shell", OodAppkit.shell.url(host: "ruby").to_s %>

<%# Link to launch Shell app in specified directory %>
<%= link_to "Shell in /path/to/dir", OodAppkit.shell.url(path: "/path/to/dir").to_s %>

<%# Link to launch Shell app for specified host in directory %>
<%= link_to "Ruby in /path/to/dir", OodAppkit.shell.url(host: "ruby", path: "/path/to/dir").to_s %>

You can change the options using environment variables:

OOD_SHELL_URL='/pun/sys/shell'
OOD_SHELL_TITLE='Shell'

Or by modifying the configuration in an initializer:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  # Defaults
  config.shell = OodAppkit::Urls::Shell.new title: 'Shell', base_url: '/pun/sys/shell'
end

This mounts all the files under the OodAppkit.dataroot using the following route by default:

# config/routes.rb

mount OodAppkit::FilesRackApp.new => '/files', as: :files

To disable this generated route:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  config.routes.files_rack_app = false
end

To add a new route:

# config/routes.rb

# rename URI from '/files' to '/dataroot'
mount OodAppkit::FilesRackApp.new => '/dataroot', as: :files

# create new route with root set to '/tmp' on filesystem
mount OodAppkit::FilesRackApp.new(root: '/tmp') => '/tmp', as: :tmp

This gem comes with a wiki static page engine. It uses the supplied markdown handler to display GitHub style wiki pages.

By default the route is generated for you:

# config/routes.rb

get 'wiki/*page' => 'ood_appkit/wiki#show', as: :wiki, content_path: 'wiki'

and can be accessed within your app by

<%= link_to "Documentation", wiki_path('Home') %>

To disable this generated route:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  config.routes.wiki = false
end

To change (disable route first) or add a new route:

# config/routes.rb

# can modify URI as well as file system content path where files reside
get 'tutorial/*page' => 'ood_appkit/wiki#show', as: :tutorial, content_path: '/path/to/my_tutorial'

# can use your own controller
get 'wiki/*page' => 'my_wiki#show', as: :wiki, content_path: 'wiki'

You can use your own controller by including the appropriate concern:

# app/controllers/my_wiki_controller.rb
class MyWikiController < ApplicationController
  include OodAppkit::WikiPage

  layout :layout_for_page

  private
    def layout_for_page
      'wiki_layout'
    end
end

And add a show view for this controller:

<%# app/views/my_wiki/show.html.erb %>

<div class="ood-appkit markdown">
  <div class="row">
    <div class="col-md-8 col-md-offset-2">
      <%= render file: @page %>
    </div>
  </div>
</div>

You can easily override any bootstrap variable using environment variables:

# BOOTSTRAP_<variable>='<value>'

# Change font sizes
BOOTSTRAP_FONT_SIZE_H1='50px'
BOOTSTRAP_FONT_SIZE_H2='24px'

# Re-use variables
BOOTSTRAP_GRAY_BASE='#000'
BOOTSTRAP_GRAY_DARKER='lighten($gray-base, 13.5%)'
BOOTSTRAP_GRAY_DARK='lighten($gray-base, 20%)'

The variables can also be overridden in an initializer:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  # These are the defaults
  config.bootstrap.navbar_inverse_bg = '#53565a'
  config.bootstrap.navbar_inverse_link_color = '#fff'
  config.bootstrap.navbar_inverse_color = '$navbar-inverse-link-color'
  config.bootstrap.navbar_inverse_link_hover_color = 'darken($navbar-inverse-link-color, 20%)'
  config.bootstrap.navbar_inverse_brand_color = '$navbar-inverse-link-color'
  config.bootstrap.navbar_inverse_brand_hover_color = '$navbar-inverse-link-hover-color'
end

You MUST import the bootstrap overrides into your stylesheets for these to take effect

// app/assets/stylesheets/application.scss

// load the bootstrap sprockets first
@import "bootstrap-sprockets";

// this MUST occur before you import bootstrap
@import "ood_appkit/bootstrap-overrides";

// this MUST occur after the bootstrap overrides
@import "bootstrap";

Note: After changing an environment variable or configuration option in the initalizer you must clobber your assets and restart the app:

# clobber assets
bin/rake assets:clobber

# restart app
touch tmp/restart.txt

A simple markdown handler is included with this gem. Any views with the extensions *.md or *.markdown will be handled using the Redcarpet gem. The renderer can be modified as such:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  # Default
  config.markdown = Redcarpet::Markdown.new(
    Redcarpet::Render::HTML,
    autolink: true,
    tables: true,
    strikethrough: true,
    fenced_code_blocks: true,
    no_intra_emphasis: true
  )
end

Really any object can be used that responds to #render.

Note: You will need to import the appropriate stylesheet if you want the rendered markdown to resemble GitHub's display of markdown.

// app/assets/stylesheets/application.scss

// load the bootstrap sprockets first
@import "bootstrap-sprockets";

// this MUST occur before you import bootstrap
@import "ood_appkit/bootstrap-overrides";

// this MUST occur after the bootstrap overrides
@import "bootstrap";

// this MUST occur after the bootstrap import
@import "ood_appkit/markdown";

It is also included if you import the default stylesheet:

// app/assets/stylesheets/application.scss

// load the bootstrap sprockets first
@import "bootstrap-sprockets";

// this MUST occur before you import bootstrap
@import "ood_appkit/bootstrap-overrides";

// this MUST occur after the bootstrap overrides
@import "bootstrap";

// this MUST occur after the bootstrap import
@import "ood_appkit";

A custom log formatter is provided, along with lograge, to both reduce the amount of unnecessary logging in production but properly prefix each log with timestamp, log severity, and the name of the application. By default enable_log_formatter is set to true for the production environment, but you can turn it on all the time by using an initializer:

# config/initializers/ood_appkit.rb

OodAppkit.configure do |config|
  # Default
  config.enable_log_formatter = true
end

This does several things things:

1. enable lograge

2. call OodAppkit::LogFormatter.setup which

   • sets the formatter of the Rails logger to an instance of OodAppkit::LogFormatter
   • and sets the progname of the Rails logger to the APP_TOKEN env var if it is set

In production, a single log will look like:

[2016-06-20 10:23:59 -0400 sys/dashboard]  "INFO method=GET path=/pun/dev/dashboard/ format=html controller=dashboard action=index status=200 duration=297.15 view=290.20"

To take advantage of branding features you must import it in your stylesheet:

// app/assets/stylesheets/application.scss

// load the bootstrap sprockets first
@import "bootstrap-sprockets";

// this MUST occur before you import bootstrap
@import "ood_appkit/bootstrap-overrides";

// this MUST occur after the bootstrap overrides
@import "bootstrap";

// this MUST occur after the bootstrap import
@import "ood_appkit/branding";

It is also included if you import the default stylesheet:

// app/assets/stylesheets/application.scss

// load the bootstrap sprockets first
@import "bootstrap-sprockets";

// this MUST occur before you import bootstrap
@import "ood_appkit/bootstrap-overrides";

// this MUST occur after the bootstrap overrides
@import "bootstrap";

// this MUST occur after the bootstrap import
@import "ood_appkit";

One such branding feature is the navbar-breadcrumbs. It is used to accentuate the tree like style of the app in the navbar. It is used as such:

<nav class="ood-appkit navbar navbar-inverse navbar-static-top" role="navigation">
  <div class="navbar-header">
    ...
    <ul class="navbar-breadcrumbs">
      <li><%= link_to OodAppkit.dashboard.title, OodAppkit.dashboard.url.to_s %></li>
      <li><%= link_to 'MyApp', root_path %></li>
      <li><%= link_to 'Meshes', meshes_path %></li>
    </ul>
  </div>

  ...
</nav>

Note that you must include ood-appkit as a class in the nav tag. The breadcrumbs style will resemble the navbar-brand style.

Access to a list of clusters defined by the system administrator on a given host is done through:

# An enumerable list of clusters
OodAppkit.clusters
#=> #<OodCore::Clusters>

# Count number of clusters available
OodAppkit.clusters.count
#=> 3

# Check if cluster called "tiny_cluster" exists
OodAppkit.clusters.include? :tiny_cluster
#=> true

You can access a given cluster with id my_cluster by:

# Get object describing my HPC center's `my_cluster`
OodAppkit.clusters[:my_cluster]
#=> #<OodCore::Cluster>

# or...
OodAppkit.clusters["my_cluster"]
#=> #<OodCore::Cluster>

# Trying to access a non-existant cluster
OodAppkit.clusters[:invalid_cluster]
#=> nil

You can read more about this cluster object at https://github.com/OSC/ood_core.

The list of clusters generated by OodAppkit can be modified by supplying a different config file through the environment variable OOD_CLUSTERS

OOD_CLUSTERS="/path/to/my/config.yml"

Or a directory with cluster named configuration files (name of file is id of cluster):

OOD_CLUSTERS="/path/to/configs.d"

The default location is: /etc/ood/config/clusters.d

Generated using:

rails plugin new ood_appkit --full --skip-bundle

This gem is released under the MIT License.