Contents

--- !ruby/object:Gem::Specification 
name: volatiledb
version: !ruby/object:Gem::Version 
  prerelease: 
  version: 0.0.1
platform: ruby
authors: 
- Sebastian Wittenkamp (bitops)
autorequire: 
bindir: bin
cert_chain: []

date: 2012-01-04 00:00:00 Z
dependencies: []

description: "  The VolatileDB gem allows you to specify a key and an action yielding a particular piece of data.\n  \n  This data will be stored in the /tmp folder of the file system you are currently running on. Data is accessible\n  by key. Data will be read and written to storage using File.read() and File.open() -- that's it. It's up to the\n  consuming application to serialize and deserialize data correctly. All VolatileDB does is push and pull data to\n  the FS. \n  \n  If the underlying file supporting the data is found to be missing, it will be re-initialized.\n  \n  This gets to the main idea behind VolatileDB: use it to persist data that is transient and can be re-seeded \n  periodically as conditions change. \n"
email: 
- [e-mail]
executables: []

extensions: []

extra_rdoc_files: []

files: 
- .gitignore
- Gemfile
- Rakefile
- lib/volatiledb.rb
- lib/volatiledb/version.rb
- volatiledb.gemspec
homepage: http://rubygems.org/gems/volatiledb
licenses: []

post_install_message: 
rdoc_options: []

require_paths: 
- lib
required_ruby_version: !ruby/object:Gem::Requirement 
  none: false
  requirements: 
  - - ">="
    - !ruby/object:Gem::Version 
      version: "0"
required_rubygems_version: !ruby/object:Gem::Requirement 
  none: false
  requirements: 
  - - ">="
    - !ruby/object:Gem::Version 
      version: "0"
requirements: []

rubyforge_project: volatiledb
rubygems_version: 1.8.5
signing_key: 
specification_version: 3
summary: VolatileDB is a simple stupid storage solution for transient data on transient filesystems.
test_files: []

Package Spec version

volatiledb-0.0.1