ActiveRecord::NoEnvironmentInSchemaError:
Environment data not found in the schema. To resolve this issue, run:
bin/rails db:environment:set RAILS_ENV=development
Tasks: TOP => db:migrate:reset => db:drop => db:check_protected_environments
(See full trace by running task with --trace)
対処
rake db:migrate:status
上記のコマンドでdbのステータスを確認します。
⬇︎実行内容
up 20201013130002 Devise create users
down 20201015132219 Add devise to users
再度、下記実行 $ git commit -a -m "Update Gemfile for Heroku" $ git push heroku master
remote: LoadError: cannot load such file -- uglifierは消えたが error: failed to push some refs to~は変わらず。
$ git push heroku master実行時のエラーに下記があった。
remote: ###### WARNING:
remote:
remote: This buildpack was created as a stop-gap measure to allow running applications with Bundler 2 on Heroku.
remote: Heroku now supports Bundler 2 directly: https://devcenter.heroku.com/changelog-items/1563
remote:
remote: Please discontinue use of this buildpack and instead directly use the `heroku/ruby` buildpack.
remote:
remote: To remove this buildpack use the `heroku buildpacks` command to list your existing buildpacks.
remote:
remote: If you only have one buildpack listed you can run:
remote:
remote: ```
remote: heroku buildpacks:set heroku/ruby
remote: ```
remote:
remote: If you have multiple buildpacks, you'll need to add the buildpack to the correct location using
remote: `heroku buildpacks:add heroku/ruby -i <correct index>` and then remove this buildpack via:
remote:
remote: ```
remote: heroku buildpacks:remove https://github.com/bundler/heroku-buildpack-bundler2
remote: ```
Buildpack set. Next release on pacific-atoll-18588 will use heroku/ruby.
Run git push heroku main to create a new release using this buildpack.
再度$ git push heroku masterすると今度は下記の警告。
remote: webpack binstubs not found.
remote: Have you run rails webpacker:install ?
remote: Make sure the bin directory or binstubs are not included in .gitignore
remote: Exiting!
remote: webpack binstubs not found.
remote: Have you run rails webpacker:install ?
remote: Make sure the bin directory or binstubs are not included in .gitignore
remote: Exiting!
$ git push heroku mainを実行。
error: src refspec main does not match any
error: failed to push some refs to 'https://git.heroku.com/*****.git'
$ git push heroku main -fで強制プッシュしようとしても同じ結果だったので
gitのリポジトリを削除・再作成し、herokuのアプリも再作成してadd、commit、pushを行ったが、
以下のエラーは消えず…
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/*****.git'
ダメ元で再度$ git push heroku main -fを実行したところ、ようやく完了。
無意味なダウンロード等を結構してしまったと思うのでこの後無事に動作するのかが不安…
classCommandendclassBegin<CommandendclassRollback<CommandendclassCommit<CommandendclassRead<Commandattr_reader:vardefinitialize(var)@var=varendendclassWrite<Commandattr_reader:var,:valdefinitialize(var,val)@var=var@val=valendendclassLockattr_reader:tr,:var,:typedefinitialize(tr,var,type)@tr=tr@var=var@type=typeendendclassUnlockattr_reader:tr,:vardefinitialize(tr,var)@tr=tr@var=varendendclassInsertattr_reader:var,:valdefinitialize(var,val)@var=var@val=valendendclassDeleteattr_reader:vardefinitialize(var)@var=varendendclassEventattr_reader:tr,:cmd# tr :String# cmd : Commanddefinitialize(tr,cmd)@tr=tr@cmd=cmdendendclassDatabaseattr_reader:vars# vars : Map<var_name,value>definitialize(vars)@vars=varsendendclassTransactionattr_accessor:name,:varsdefinitialize(name)@name=name@vars={}endendclassStateattr_reader:db,:events,:pointer,:trsdefinitialize(db,events,trs)@db=db@locks=[]@events=events@pointer=0@trs=trsenddefnext()e=@events[@pointer]ifethenife.cmd.is_a?(Begin)thenputs"Begin #{e.tr}"elsife.cmd.is_a?(Rollback)thenputs"Rollback #{e.tr}"elsife.cmd.is_a?(Commit)thenputs"Commit #{e.tr}"elsife.cmd.is_a?(Read)thenif@locks.filter{|l|l.tr!=e.tr&&l.var==e.cmd.var&&l.type==:Exclusive}.empty?thenputs"Read #{e.tr} var=#{e.cmd.var} => val=#{@db.vars[e.cmd.var]}"elseputs"Read #{e.tr} var=#{e.cmd.var} => Read failed. This variable is locked by another transaction."raise("Reading failure")endelsife.cmd.is_a?(Write)thenif@locks.filter{|l|l.tr!=e.tr&&l.var==e.cmd.var}.empty?thenpre=@db.vars[e.cmd.var]@db.vars[e.cmd.var]=e.cmd.valputs"Write #{e.tr} var=#{e.cmd.var} val=#{e.cmd.val} => db[#{e.cmd.var}]: #{pre} => #{@db.vars[e.cmd.var]}"elseputs"Write #{e.tr} var=#{e.cmd.var} val=#{e.cmd.val} => This variable is locked by another transaction."raise("Writing failure")endelsife.cmd.is_a?(Lock)thenif@locks.filter{|l|l.tr!=e.cmd.tr&&l.var==e.cmd.var&&l.type==:Exclusive}.empty?then@locks<<e.cmdputs"Lock #{e.tr} var=#{e.cmd.var} type=#{e.cmd.type} => Success."elseputs"Lock #{e.tr} var=#{e.cmd.var} type=#{e.cmd.type} => This variable is locked by another transaction. Getting lock was failed."raise("Locking failure")endelsife.cmd.is_a?(Unlock)then@locks.filter!{|l|!(l.tr==e.tr&&l.var==e.cmd.var)}puts"Unlock #{e.tr}"elsife.cmd.is_a?(Insert)thenif@db.vars[e.cmd.var].nil?then@db.vars[e.cmd.var]=e.cmd.valputs"Insert #{e.tr} var=#{e.cmd.var} val=#{e.cmd.val} => Success."elseputs"Insert #{e.tr} var=#{e.cmd.var} val=#{e.cmd.val} => This variable is already exists. Insertion was failed."raise("Insertion failure")endelsife.cmd.is_a?(Delete)thenif!@locks.filter{|l|l.tr!=e.tr&&l.var==e.cmd.var}.empty?thenputs"Delete #{e.tr} var=#{e.cmd.var} => This variable is locked by another transaction. Deletion was failed."raise("Deletion failure")endif@db.vars[e.cmd.var].nil?thenputs"Delete #{e.tr} var=#{e.cmd.var} => No such variable. Deletion was failed."raise("Deletion failure")end@db.vars.delete(e.cmd.var)@locks.filter!{|l|!(l.tr==e.tr&&l.var==e.cmd.var)}puts"Delete #{e.tr} var=#{e.cmd.var} => Success"elseputs"Other"endelse# the last of eventsend@pointer+=1endend@events=[Event.new("tr_a",Begin.new()),Event.new("tr_b",Begin.new()),Event.new("tr_a",Lock.new("tr_a","X",:Shared)),Event.new("tr_a",Read.new("X")),Event.new("tr_b",Read.new("X")),Event.new("tr_a",Lock.new("tr_a","X",:Exclusive)),Event.new("tr_a",Write.new("X",20)),Event.new("tr_a",Unlock.new("tr_a","X")),Event.new("tr_b",Read.new("X")),Event.new("tr_b",Insert.new("Y",12)),Event.new("tr_b",Delete.new("Y")),Event.new("tr_a",Commit.new()),Event.new("tr_b",Commit.new())]@vars={"X"=>10}@db=Database.new(@vars)@trs={"tr_a"=>Transaction.new("tr_a"),"tr_b"=>Transaction.new("tr_b"),}@state=State.new(@db,@events,@trs)@events.each_index{|i|printf("%3d ",i)@state.next()}
class Scene < ApplicationRecord
belongs_to :user
has_one_attached :image
省略
end
変更後
class Scene < ApplicationRecord
belongs_to :user
has_many_attached :images
省略
end
2.コントローラーの変更
変更前
class ScenesController < ApplicationController
def new
@scene = Scene.new
end
def create
@scene = Scene.new(scene_params)
if @scene.save
redirect_to root_path
else
render :new
end
end
def show
@scene = Scene.find(params[:id])
end
private
def scene_params
params.require(:scene).permit(:name, :user_name, :comment, :image).merge(user_id: current_user.id)
end
end
変更後
class ScenesController < ApplicationController
def new
@scene = Scene.new
end
def create
@scene = Scene.new(scene_params)
if @scene.save
redirect_to root_path
else
render :new
end
end
def show
@scene = Scene.find(params[:id])
end
private
def scene_params
params.require(:scene).permit(:name, :user_name, :comment, image: []).merge(user_id: current_user.id)
end
end
Active Storageは、ファイルアップロードを行うための機能です。これを使えば、フォームで画像の投稿機能などが簡単に作れます。クラウドストレージサービス(Amazon S3, Google Cloud Storage, Microsoft Azure Storageなど)に対するファイルのアップロードを簡単に行うことができます。
#rails db:migrate:stauts 実行結果
database: アプリ名_development
Status Migration ID Migration Name
--------------------------------------------------
up 20201001015223 Create orders
up 20201001092756 Create addresses
up 20201014023427 Add id to addresses
up 20201014030100 Add id to orders
database: アプリ名_development
Status Migration ID Migration Name
--------------------------------------------------
up 20201001015223 Create orders
up 20201001092756 Create addresses
up 20201014023427 Add id to addresses
down 20201014030100 Add id to orders
database: アプリ名_development
Status Migration ID Migration Name
--------------------------------------------------
up 20201001015223 Create orders
up 20201001092756 Create addresses
down 20201014023427 Add id to addresses
down 20201014030100 Add id to orders
登録したメールアドレスがLogged in asの後に表示されていればログイン成功
