sqlite - When should I restart Rails Server while in the development environment -

sqlite - When should I restart Rails Server while in the development environment -

this answer 5 years old , wasn't specific.

i lost couple of hours in development. code worked after server restart. can't sure, think because of alter made scoped validation in model:

validates :name, presence: true , uniqueness: {scope: :institution_id}

this year old answer doesn't seem apply situation. in particular, rule not seem have held me:

"the general rule of thumb here making changes outside of app/ or config/routes.rb require restart."

is there other rule consider? while developing, i'd avoid restarting server much possible.

i suppose 1 valid reply this answer still correct. if gets upvoted enough, i'll assume remains accurate , adventure debugging-that-was-fixed-with-a-server-restart other-yet-to-be-defined issue.

addendum: using:

mac os 10.9.5 rails 4.1.5 spring 1.1.3

server startup:

[2014-10-12 09:29:29] info webrick 1.3.1 [2014-10-12 09:29:29] info ruby 2.1.2 (2014-05-08) [x86_64-darwin13.0] [2014-10-12 09:29:29] info webrick::httpserver#start: pid=9366 port=3000

i assume using osx? should seek using pow server restarts automatically when needs to.

if using rails 4.1+ consider setting spring. way there no need manually start/stop background processes or restarting rails server after made changes require restart.

ruby-on-rails sqlite development-environment webrick