Contents

# -*- encoding: utf-8 -*-
$:.push File.expand_path("../lib", __FILE__)
require "volatiledb/version"

Gem::Specification.new do |s|
  s.name        = "volatiledb"
  s.version     = Volatile::VERSION
  s.authors     = ["Sebastian Wittenkamp (bitops)"]
  s.email       = ["[e-mail]"]
  s.homepage    = "https://github.com/bitops/volatiledb"
  s.summary     = %q{VolatileDB is a simple stupid storage solution for transient data on transient filesystems.}
  s.description = <<DESC
  The VolatileDB gem allows you to specify a key and an action yielding a particular piece of data.
  
  This data will be stored in the /tmp folder of the file system you are currently running on. Data is accessible
  by key. Data will be read and written to storage using File.read() and File.open() -- that's it. It's up to the
  consuming application to serialize and deserialize data correctly. All VolatileDB does is push and pull data to
  the FS. 
  
  If the underlying file supporting the data is found to be missing, it will be re-initialized.
  
  This gets to the main idea behind VolatileDB: use it to persist data that is transient and can be re-seeded 
  periodically as conditions change. 
DESC

  s.rubyforge_project = "volatiledb"

  s.files         = `git ls-files`.split("\n")
  s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
  s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
  s.require_paths = ["lib"]

  # specify any dependencies here; for example:
  # s.add_development_dependency "rspec"
  # s.add_runtime_dependency "rest-client"
end

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
volatiledb-1.0.0	volatiledb.gemspec
volatiledb-0.0.4	volatiledb.gemspec
volatiledb-0.0.3	volatiledb.gemspec
volatiledb-0.0.2	volatiledb.gemspec