Tags

employment
llc
xrp
redhat
ripple
interfaces
ncurses
ruby
refs
filesystems
retro gaming
raspberry pi
sinatra
3d printing
nethack
gcc
compiler
fedora
virtfs
project
gaming
vim
grep
sed
aikido
philosophy
splix
android
lvm
storage
bitcoin
projects
sig315
miq
db
polisher
meditation
hopex
conferences
omega
simulator
bundler_ext
rubygems
book review
google code in
isitfedoraruby
svn
gsoc
design patters
jsonrpc
rjr
aeolus
ohiolinuxfest
rome
europe
travel
brno
gtk
python
puppet
conference
fudcon
html5
snap
tips
ssh
linux
hardware
libvirt
virtualization
engineering expo
cloud
redmine
plugins
rpm
yum
rake
screencasting
jruby
fosscon
pidgin
gnome-shell
distros
notacon
presentation
rails
deltacloud
apache
qmf
passenger
syrlug
hackerspace
music
massive attack
backups
crypto
vnc
xsd
rxsd
x3d
mercurial
webdev
ovirt
qpid
haikus
poetry
legaleese
jquery
selenium
testing
xpath
git
sshfs
svg
ldap
autotools
pygtk
xmlrpc
slackware

Nov 3 2009 ruby rails

Word of warning about rails 2.3

Rails in Fedora was upgraded to 2.3 in F11. When working on oVirt today, I discovered that changes to my templates were not being served to the user until I restarted mongrel/rails. Quickly searching around for the issue, I stumbled upon the Rails 2.3 changelog, particularly this section which states:

In most cases, you’ll want template caching to be turned on in production, which you can do by making a setting in your production.rb file: config.actionview.cachetemplate_loading = true This line will be generated for you by default in a new Rails 2.3 application.

While this is an excellent default for production systems, for development this is undesired (eg you’ll need to restart mongrel every time you make a template change no matter how small), and thus adding the following to config/environment.rb resolves the issue (preferably you’ll just enable in in your dev environment, but I didn’t really care as this is on my dev box)

config.actionview.cachetemplate_loading = false