https://github.com/loopj/manifest-generator

A cache.manifest generator in ruby, for use in your HTML5 offline apps.
https://github.com/loopj/manifest-generator

Last synced: 9 months ago
JSON representation

A cache.manifest generator in ruby, for use in your HTML5 offline apps.

• Host: GitHub
• URL: https://github.com/loopj/manifest-generator
• Owner: loopj
• License: mit
• Created: 2011-11-04T01:03:05.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2015-11-09T03:50:05.000Z (over 10 years ago)
• Last Synced: 2025-08-14T10:38:48.887Z (10 months ago)
• Language: Ruby
• Homepage:
• Size: 129 KB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

          
Manifest Generator

================

A cache.manifest generator in ruby, for use in your HTML5 offline apps.

The configuration DSL is designed to map closely to the keywords in the HTML5 

cache manifest syntax: 

Configuration

=============

    # Build up the cache manifest

    manifest = ManifestDestiny.configure do

      # Cache local files in your offline app (maps to CACHE section)

      cache "images/sound-icon.png"

      cache "images/background.png"

    

      # Cache a remote file in your offline app (maps to CACHE section)

      cache "http://ajax.googleapis.com/ajax/libs/jquery/1.6.4/jquery.min.js"

      # Online file whitelist (maps to NETWORK section)

      network "comm.cgi"

      

      # Fallback locations (maps to cache manifest FALLBACK section)

      fallback "/" => "offline.html"

    end

Generate a Cache Manifest

=============

    manifest.to_s

Render a Cache Manifest in Rails 2.x

====================================

    render_manifest do

      # Same configuration syntax as above

      cache "images/sound-icon.png"

      cache "images/background.png"

    end

Contributing to manifest-destiny

================================

* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet

* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it

* Fork the project

* Start a feature/bugfix branch

* Commit and push until you are happy with your contribution

* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.

* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright

=========

Copyright (c) 2011 James Smith. See LICENSE.txt for

further details.