Databases
StackOverflow2013
Postsdbo
POIssue(s) Deploying Rails app (SQLite3) to Heroku (PostgreSQL)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIssue(s) Deploying Rails app (SQLite3) to Heroku (PostgreSQL)
    primarykey
    data
    text
    <p>I see numerous posts regarding issues with deploying to Heroku, but I haven't been able to find the solution for my case. Any input would be much appreciated.</p> <p>I have a blogging application that runs fine locally. However, I am returning "I'm sorry, but something went wrong" when I deploy to Heroku. </p> <p>The gems I have are:</p> <pre><code>group :development do gem 'sqlite3', '1.3.5' end group :production do gem 'pg', '0.12.2' end </code></pre> <p>The steps I've taken are:</p> <pre><code>git add. git commit -am "latest update" git push git push heroku rake db:migrate heroku run rake db:migrate </code></pre> <p>My SQLite3 database is migrating fine, as I can find my latest blog entry (Blog.find(21)) through rails console. However, the data does not seem to be migrating to the Heroku database, as the Heroku console returns </p> <pre><code>"ActiveRecord::RecordNotFound: Couldn't find Blog with id=21." </code></pre> <p>Additionally, "heroku logs" finds:</p> <pre><code>Completed 500 Internal Server Error in 50ms NoMethod Error (undefined method 'blogs' for nil:NilClass): app/controllers/static_pages_controller.rb:8:in 'home' </code></pre> <p>Does this mean there could be an issue in my static_pages_controller, or is it just returning an error because the database is not migrating correctly?</p> <p>Below is my static_pages controller, which works fine on my local server.</p> <pre><code>class StaticPagesController &lt; ApplicationController def home if signed_in? @blog = current_editor.blogs.build end @editor = Editor.first @blogs = @editor.blogs.paginate(page: params[:page]) end end </code></pre> <p>Note: I am using Editor.first above because I (ie. editor_id: 1) will be the only editor of my blog. I just created an Editor model to store the password_digest.</p> <p>So, why isn't my application deploying on Heroku? </p> <p>Any feedback would be appreciated. Also, please let me know if you need to see additional files, and I will attach. </p> <p>Thanks so much!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmu is too short
    1. USumezo
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIssue(s) Deploying Rails app (SQLite3) to Heroku (PostgreSQL)
      1. USuser1287523
      1. VTFavorite
    1. COCan you confirm you are pushing data from the correct local db? ie. Make sure you are NOT pushing like an empty production db or something up to Heroku? Maybe output from the data push would be useful?
      singulars
      1. POIssue(s) Deploying Rails app (SQLite3) to Heroku (PostgreSQL)
      1. USMario Zigliotto
    2. COThanks SizzlePants. It seems that was the problem. However, I'm still not sure why I'd get "I'm sorry but something went wrong" message, even with an empty database. Shouldn't the Heroku deployment work (albeit with an empty site), as long as the columns are migrated correctly?
      singulars
      1. POIssue(s) Deploying Rails app (SQLite3) to Heroku (PostgreSQL)
      1. USumezo
    3. COHeroku does handle that w/o any issue. I would expect that your views / code may make calls that assume an object's method should be available.... but actually are NOT due to nto having any data. An example would be if you had something you expected to be a string, then did like my_str.captialize ... if my_str was a nil object or not even a string... u would get an error.
      singulars
      1. POIssue(s) Deploying Rails app (SQLite3) to Heroku (PostgreSQL)
      1. USMario Zigliotto
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload