-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
builds with ruby 2.1.1... Heroku requires ruby 2.5.8 #2
Comments
Thanks for your initiative. Shouldn't be too hard because it's already running on heroku with postgres, see http://plutopluto.herokuapp.com, for example. Sorry, the starter code is a little outdated (but the good news not much changed as far as I can tell / remember). About sqlite3 - the fix is changing the entry in Gemfile from pluto to pluto-models. About ruby 2.1.1 - I deleted the Gemfile.lock with the outdated versions - what else - not sure - sorry - I try to help out. Keep going. Cheers. Prost. |
ok progress :) I made a fresh clone and tried again with current releases of ruby (2.6.5 + 2.7.0) The build was successful (I wonder how many times I needed but just didn't realize now, when running
|
Hard to tell - sorry I have no clue - can you post the error stack trace (backtrace)? Not sure if it's included in the rake error otherwise try with verbose e.g. $ |
verbose didn't do much so I tried trace:
|
Thanks for the backtrace - that helps - the error is in line https://github.com/feedreader/pluto/blob/master/pluto-models/lib/pluto/connecter.rb#L67 db_config should be a structure and NOT a string - not sure why - I will have to try to do a setup over here (sorry that might take some time). Notes: It's caused by Rails 6 change in ActiveRecord::Base.configuration, see https://blog.bigbinary.com/2019/03/19/rails-6-changed-activerecord-base-configurations-result-to-an-object.html |
A quick hack that may work (sorry I cannot test / try now) - add in config/boot.rb the line before Pluto.connect!
and than retry (that should clean out/clear all db configs on startup). |
sorry, no luck there. All good. I've got still got some tinkering to do with my first Pluto project :) no need to get too lost into setting up another, just yet. |
trying to get this running on heroku (and configure a "deploy to heroku" button), but running into some versioning issues
Not sure how much trouble you're inclined to go through for this...
another thing, heroku doesn't allow sqlite3, only postgress, nor does it allow sqlite even for development (only wants pg so dev and production are the same).
Right now I'm just trying to run it locally so I did
bundle install
, even not including "--without production", it still seems to be looking for sqlite3.now I'm off to google postgress and see what I can gather.
(update, did get it to build and deploy locally with sqlite.. still digging around on postgress.. assuming I need to set up a db first and use that in my environment)
The text was updated successfully, but these errors were encountered: