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
{{ message }}
Repository navigation
builds with ruby 2.1.1... Heroku requires ruby 2.5.8 #2
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)
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.
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. $ rake --verbose setup PLANET=ruby. If I get around I will try a setup over here (it might take a day or two sorry).
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.
Activity
geraldb commentedon May 19, 2020
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.
infominer33 commentedon May 19, 2020
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
rm Gemfile.lock)now, when running
% rake setup PLANET=rubyI get:geraldb commentedon May 19, 2020
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. $
rake --verbose setup PLANET=ruby. If I get around I will try a setup over here (it might take a day or two sorry).infominer33 commentedon May 19, 2020
verbose didn't do much so I tried trace:
geraldb commentedon May 19, 2020
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
geraldb commentedon May 19, 2020
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).
infominer33 commentedon May 19, 2020
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.