Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Added support for new manifest format used by turbo-sprockets-rails3, and possibly Rails #110

wants to merge 1 commit into


None yet
3 participants

Hi there,

I've recently developed a gem that speeds up the asset compilation task, called turbo-sprockets-rails3.
In order for it to do its magic, it needs to alter the manifest.yml format to include both :source_digests and :digest_files, instead of a flat digest files hash.

This pull request simply looks for the presence of the :digest_files key in manifest.yml, and falls back to the old format it it's not found, so it should be 100% backwards compatible.

Note that I'm also trying to get the patch merged into Rails 4.0.0, and possibly Rails 3.2.9 (see rails/sprockets-rails#21). Even if it's not merged into Rails for some reason, I would really appreciate it if you could support the users of the turbo-sprockets-rails3 gem.

Thanks for your time!

@ndbroadbent ndbroadbent referenced this pull request in ndbroadbent/turbo-sprockets-rails3 Oct 2, 2012


Compatibility with asset_sync gem #4

(you might want to add jruby-head to your list of 'Allowed Failures' on Travis)

rgarver commented Oct 12, 2012

👍 Would love to see this pulled in. Lots of small JS files is slowing my deploys and cukes and this is the last piece to making the new turbo-sprockets system play nice with my dependencies.


davidjrice commented Oct 22, 2012

Hey, so I've started pulling this in and testing it.

Started branch in rumblelabs/asset_sync#turbosprockets

Just had a first successful deployment of one app. Will run a few more tests and get this out this week :)

Hi there, I got some good advice from Jeremy Kemper, which was to keep the manifest.yml file the same, and add a new sources_manifest.yml file for source digests. I've done that now, so this pull request is no longer needed (manifest.yml is now unchanged.)

I've released this change in version 0.2.0. Sorry about the noise!


davidjrice commented Oct 25, 2012

@ndbroadbent cool, no worries.

I've opened another issue then, #118 to discuss some documentation improvements regarding turbosprockets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment