Merge pull request #22 from dalizard/add-ruby-3-support-to-example-app

Add Ruby 3 support to the example app

example/Gemfile

@@ -2,13 +2,14 @@
 
 source 'https://rubygems.org'
 
-gem 'rails', '6.0.2.1'
+gem 'rails', '6.1.5'
 
 gem 'bootstrap-sass'
 gem 'jquery-rails'
 gem 'rspec-rails'
 gem 'sass-rails', '~> 5.0.0'
 gem 'slim'
 gem 'sqlite3'
+gem 'webrick', '~> 1.8'
 gem 'will_paginate'
 gem 'will_paginate-bootstrap'

example/config/boot.rb

@@ -1,4 +1,4 @@
 # Set up gems listed in the Gemfile.
 ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../../Gemfile', __FILE__)
 
-require 'bundler/setup' if File.exists?(ENV['BUNDLE_GEMFILE'])
+require 'bundler/setup' if File.exist?(ENV['BUNDLE_GEMFILE'])

example/db/schema.rb

@@ -2,8 +2,8 @@
 # of editing this file, please use the migrations feature of Active Record to
 # incrementally modify your database, and then regenerate this schema definition.
 #
-# This file is the source Rails uses to define your schema when running `rails
-# db:schema:load`. When creating a new database, `rails db:schema:load` tends to
+# This file is the source Rails uses to define your schema when running `bin/rails
+# db:schema:load`. When creating a new database, `bin/rails db:schema:load` tends to
 # be faster and is potentially less error prone than running all of your
 # migrations from scratch. Old migrations may fail to apply correctly if those
 # migrations use external dependencies or application code.
@@ -27,7 +27,7 @@
   end
 
   create_table "users", force: :cascade do |t|
-    t.string "name", limit: 255, null: false
+    t.string "name", null: false
     t.datetime "created_at"
     t.datetime "updated_at"
     t.index ["name"], name: "index_users_on_name", unique: true