You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been using the USE_FREEDESKTOP_PLACEHOLDER=true approach and it's worked fine for our apps that are deployed elsewhere. But today I tried this approach for a Heroku-deployed app, and I get the following error. The bundle exec rake -P command works fine locally, but the dummy.xml file it's apparently looking for in the Heroku build/deploy environment is not there on my local system either.
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.7.3
-----> Installing dependencies using bundler 1.17.3
Running: BUNDLE_WITHOUT='development:test' BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 BUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE=1 bundle install -j4
Using rake 13.0.1
[...]
Using mimemagic 0.3.10
[...]
Bundle complete! 25 Gemfile dependencies, 62 gems now installed.
Gems in the groups development and test were not installed.
Bundled gems are installed into `./vendor/bundle`
Removing bundler (1.17.3)
Bundle completed (0.47s)
Cleaning up the bundler cache.
-----> Installing node-v12.16.2-linux-x64
-----> Detecting rake tasks
!
! Could not detect rake tasks
! ensure you can run `$ bundle exec rake -P` against your app
! and using the production group of your Gemfile.
! rake aborted!
! Errno::ENOENT: No such file or directory @ rb_sysopen - /tmp/build_f6907ac1/vendor/bundle/ruby/2.7.0/gems/mimemagic-0.3.10/dummy.xml
The text was updated successfully, but these errors were encountered:
Looking at how USE_FREEDESKTOP_PLACEHOLDER is implemented, I don't think you can get it to work on Heroku (or any other platform where build step is separated from run step).
Maybe instead you could try creating an empty file manually (somewhere in your code) and point FREEDESKTOP_MIME_TYPES_PATH env var to it?
We've been using the
USE_FREEDESKTOP_PLACEHOLDER=true
approach and it's worked fine for our apps that are deployed elsewhere. But today I tried this approach for a Heroku-deployed app, and I get the following error. Thebundle exec rake -P
command works fine locally, but thedummy.xml
file it's apparently looking for in the Heroku build/deploy environment is not there on my local system either.My app details:
The Heroku build/deploy error:
The text was updated successfully, but these errors were encountered: