all. Has anyone had success deploying previewable Active Storage on Heroku. I followed the guidance on the Heroku Devcenter, added the buildpack, but still no love. When running which ffmeg or which poppler from heroku bash, I get no response which indicates that the necessary binaries did not get installed.
Any ideas?
Related
As of this morning, without having change anything in my Heroku CLI setup, I received the following error when I tried to run:
heroku logs -t -app <app_name>
! Please specify a version along with Heroku's API MIME type. For example, Accept: application/vnd.heroku+json; version=3.
I have since tried updating both heroku and heroku-toolbelt via brew upgrade heroku and brew upgrade heroku-toolbelt, but this did not solve the issue.
I get this error essentially whenever I try to do anything with heroku CLI, including heroku logs, heroku apps, heroku login, and heroku auth:login.
I am running MacOS, and the error posted is the only information that I am getting back from Heroku.
This discussion here: How can I specify heroku's MIME type? pertains to upgrading Heroku in Ubuntu and does not solve my issue.
I had the same problem -- but installing the new Toolbelt did not work at first. There was one other step I needed to do.
from: https://devcenter.heroku.com/articles/heroku-cli
It has instructions for each platform on installing the new cli -- and says you need to run: which heroku in order to verify the proper version is running. In my case I also needed to do a gem uninstall heroku in order to get everything working, as it was running the gem binary instead of the newly installed heroku-cli binary.
If you were using heroko Plugin for intellij
I tried alot to make it work !
From here official response
#emzeidan thanks for the report. This plugin is deprecated, and uses an old version of the Heroku API that has been shut down. Please recommend to your users that they use one of the alternative deployment mechanisms described in our DevCenter article on WAR deployment. If you can remove from the plugin from any Bamboo marketplace (or similar thing) that would be helpful too. Thanks.
This was on Sept-2017
I run the 'heroku --version' command and the toolbelt automatically updates the client. After that the login was ok.
I had the same problem on macOS Sierra 10.12.3 when I installed heroku via brew.
To get round it I ran brew uninstall heroku-toolbelt then installed via the Mac installer at https://devcenter.heroku.com/articles/heroku-cli#macos and it works fine now.
Have you specified the heroku gem in your Gemfile? If yes, then remove it.
And then, install Heroku CLI for https://devcenter.heroku.com/articles/getting-started-with-ruby#set-up and run your command.
When I try to use heroku pg:psql, the following error is displayed.
! This version of the API has been Sunset.
! Please see https://devcenter.heroku.com/changelog-items/1147 for more information.
How can I access postgresql on Heroku?
heroku pg:psql command worked a few week ago.
I develop my Rails app on the Cloud 9.
I had the same issue with my ruby on rails project since last Friday.
However, i was able to resolve this error message by update my heroku toolbelt on my mac os.
*Hint, if your heroku file was installed in project gem. you will need to delete that file.
Use command which heroku to identify where is the heroku file. if it is inside the .rvm folder that means your project is still using outdated heroku file. and simply remove it and then ran an new install heroku cli should fix this error.
Let me know if this works for you.
I am currently trying to install the CommonMarker gem on my Heroku app. I have included it in my Gemfile, and as I expected, it failed to bundle install due to cmake not being present in Heroku. I managed to install cmake on my development environment, but am at a loss how to do so for Heroku.
As I understand it, cmake is only needed during the bundle process, which will create the binary used by libcmark, which is in turn used by Commonmarker. I have read something about buildpacks, but that seems to be mainly about customizing the development environments.
Any help would be greatly helpful. Thanks.
Login to Heroku and go to the settings page for your app. Add in the following order under the Buildpacks section.
https://github.com/ello/heroku-buildpack-cmake
Ruby (official Heroku version)
Note: I was able to push to Heroku and the build was successful, but the app slug size bloated dramatically.
I need to install the GSL library on Heroku running a Rails (4.0.2) app to use some gems that depend on it.
Goal:
Install the GSL library to work with GSL and Similarity gems in Heroku.
Tried approaches:
Installing Ruby / GSL in Heroku Application: Heroku crashes after deploy. GSL gem is unable to find the lib. Trace: http://pastebin.com/CPcMUdCa
Tomwolfe's Heroku's Ruby buildpack adapted for using couchbase: Same issue.
Building Dependency Binaries for Heroku Applications: Vulcan is deprecated. More info on Heroku's Devcenter and on Github
I've tried following these steps (compiling binaries):
GSL 1.15 downloaded from ftp://ftp.gnu.org/gnu/gsl/gsl-1.15.tar.gz
Uncompressed and cd gsl-1.15
./configure
make clean
make
sudo make install
It works on my local environment but not in Heroku. Heroku doesn't allow sudo but it allows access with heroku run. The problem is that the file system is ephemeral and the dyno will only live as long as your console session.
Update:
I've also tried building my own Heroku Buildpack but I couldn't make it work. I tried using multipacks. I'm not a Heroku Buildpack expert so maybe it's the problem, I'm learning more about it to make a simple repository with an example and an extended explanation of this issue.
I had to use gsl1.16 on heroku and here is how I solved it:
First added gsl1.16 buildpack to the lists of buildpacks like
heroku buildpacks:add --index:3 git://github.com/gregory/heroku-gsl-buildpack.git#gsl-1.16
Which adds to my list of buildpacks, in my case got nodejs and ruby already. Hence --index=3
Then had to set LD_LIBRARY_PATH on heroku like
heroku config:set LD_LIBRARY_PATH=/app/vendor/gsl/lib
which points to 1.16. Seen around that some people use /app/vendor/gsl1/lib but wasn't my case.
and that's it.
I made a heroku buildpack a couple months ago for 1.15 and 1.16
just do:
heroku buildpacks:set git://github.com/gregory/heroku-gsl-buildpack.git#gsl-1.16
or
heroku buildpacks:set git://github.com/gregory/heroku-gsl-buildpack.git#gsl-1.15
You'll need to use a custom buildpack. Buildpacks allow you to define any additional dependencies outside of your project and package them with your slug which is used by the dynos. The buildpack you linked to (https://github.com/tomwolfe/heroku-buildpack-gsl-ruby) would be your best bet in getting everything working. I would open issues on their github repo if you are having issues, hopefully they can help you out
I opened a heroku account.
I followed the instructions on http://docs.heroku.com/quickstart.
I have a working rails app which I have deployed successfully elsewhere.
I have a github account that works.
I have a local git repository for my rails app.
I installed the heroku gem. It shows up in my gem list.
I typed 'heroku create' at the command prompt...
My command console showed that it was thinking about it, but did nothing. No errors. No action.
Possible related facts: I am using a Windows 7 machine. I have also failed miserably at deploying with capistrano with a similar--issue command, get no response--pattern.
I'm pretty sure now that it's a Windows issue. I don't know what exactly, it could be that the heroku gem doesn't support a Windows environment very well, or it could be something else.
However, since my original post I installed Ubuntu via VirtualBox on the same machine. From that installation I ran heroku create on the same app and it worked as expected.