Databases
StackOverflow2013
Postsdbo
PODevise No route matches [GET] "/"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODevise No route matches [GET] "/"
    primarykey
    data
    text
    <p>So I'm wanting to use Devise with my web app, and everything tested out fine on localhost, but when I uploaded it to my ec2 instance I get the error ' No route matches [GET] "/" ' and I don't know how to solve this. </p> <p>Here's my Routes.rb:</p> <pre><code>devise_for :users resources :submissions root to: 'home#index' scope "api" do get "/submissions(.:format)" =&gt; "submissions#index" get "/submissions/:id(.:format)" =&gt; "submissions#show" end get "/submissions/:id/edit(.:format)" =&gt; "submissions#edit" </code></pre> <p>And here's my Gemfile, keeping in mind that I did try it with just gem: "devise" but that didn't work either. </p> <pre><code>source 'https://rubygems.org' gem 'rails', '3.2.13' # Bundle edge Rails instead: # gem 'rails', :git =&gt; 'git://github.com/rails/rails.git' gem 'sqlite3' gem 'therubyracer' # Gems used only for assets and not required # in production environments by default. group :assets do gem 'sass-rails', '~&gt; 3.2.3' gem 'coffee-rails', '~&gt; 3.2.1' # See https://github.com/sstephenson/execjs#readme for more supported runtimes # gem 'therubyracer', :platforms =&gt; :ruby gem 'uglifier', '&gt;= 1.0.3' end gem 'jquery-rails' gem "devise", :git =&gt; "git://github.com/plataformatec/devise.git" </code></pre> <p>Here is my routes.rb on my ec2 instance:</p> <pre><code>new_user_session GET /users/sign_in(.:format) devise/sessions#new user_session POST /users/sign_in(.:format) devise/sessions#create destroy_user_session DELETE /users/sign_out(.:format) devise/sessions#destroy user_password POST /users/password(.:format) devise/passwords#create new_user_password GET /users/password/new(.:format) devise/passwords#new edit_user_password GET /users/password/edit(.:format) devise/passwords#edit PUT /users/password(.:format) devise/passwords#update cancel_user_registration GET /users/cancel(.:format) devise/registrations#cancel user_registration POST /users(.:format) devise/registrations#create new_user_registration GET /users/sign_up(.:format) devise/registrations#new edit_user_registration GET /users/edit(.:format) devise/registrations#edit PUT /users(.:format) devise/registrations#update DELETE /users(.:format) devise/registrations#destroy submissions GET /submissions(.:format) submissions#index POST /submissions(.:format) submissions#create new_submission GET /submissions/new(.:format) submissions#new edit_submission GET /submissions/:id/edit(.:format) submissions#edit submission GET /submissions/:id(.:format) submissions#show PUT /submissions/:id(.:format) submissions#update DELETE /submissions/:id(.:format) submissions#destroy root / home#index GET /api/submissions(.:format) submissions#index GET /api/submissions/:id(.:format) submissions#show GET /submissions/:id/edit(.:format) submissions#edit </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJake Stevens
    1. USJake Stevens
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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