Not compatible with Heroku and asset_packager anymore

[yholkamp]

Lately I've been trying to get this plugin running on Heroku, sadly it seems it's not compatible anymore. After installing both asset_packager and this plugin, I end up with the following error messages on deploying:

/disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/asset_packager/lib/synthesis/asset_package.rb:126:in delete': Read-only file system - /disk1/home/slugs/136826_2ce0e85_01ac/mnt/public/javascripts/base_packaged.js - Heroku has a read-only filesystem. See http://docs.heroku.com/constraints#read-only-filesystem (Errno::EROFS) from /disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/asset_packager/lib/synthesis/asset_package.rb:126:indelete_previous_build'
from /disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/asset_packager/lib/synthesis/asset_package.rb:121:in build' from /disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/asset_packager/lib/synthesis/asset_package.rb:63:inbuild_all'
from /disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/asset_packager/lib/synthesis/asset_package.rb:63:in each' from /disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/asset_packager/lib/synthesis/asset_package.rb:63:inbuild_all'
from /disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/asset_packager/lib/synthesis/asset_package.rb:62:in each' from /disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/asset_packager/lib/synthesis/asset_package.rb:62:inbuild_all'
from /disk1/home/slugs/136826_2ce0e85_01ac/mnt/vendor/plugins/heroku_asset_packager/lib/heroku_asset_packager.rb:14:in initialize_asset_packager' ... 32 levels... from /usr/local/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:ininstance_eval'
from /usr/local/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in initialize' from /home/heroku_rack/heroku.ru:1:innew'
from /home/heroku_rack/heroku.ru:1

Will you update this awesome plugin to be functional in the future?

[amasses]

Unable to reproduce, however this error will come up if you forget to add the HEROKU=1 environment variable. To confirm this is present please run (from your local project path) heroku config, and if it is not there please run heroku config:add HEROKU=1.

Hope this helps.

[cgallagher]

Im seeing a similar issue.

Does the heroku config need to be specifically =1 or as the docs on the homepage says = true?

Chris