better reloading of Jammit to handle new assets created during Guard's lifetime
This commit is contained in:
parent
eb2f282b46
commit
f35182751b
@ -9,6 +9,7 @@ module Guard
|
||||
super
|
||||
|
||||
# init stuff here, thx!
|
||||
::Jammit.load_configuration ::Jammit::DEFAULT_CONFIG_PATH
|
||||
end
|
||||
|
||||
# ================
|
||||
@ -48,8 +49,8 @@ module Guard
|
||||
|
||||
def jammit
|
||||
ensure_rails_env!
|
||||
::Jammit.load_configuration ::Jammit::DEFAULT_CONFIG_PATH
|
||||
puts "Jamming"
|
||||
::Jammit.reload!
|
||||
puts "Jamming assets..."
|
||||
::Jammit.packager.force = true
|
||||
::Jammit.packager.precache_all
|
||||
true
|
||||
|
Loading…
Reference in New Issue
Block a user