Hi,
Sometimes applying a change in RT doesn’t show up instantly in the
web UI and it requires a mason cache cleaning before the apache
restart. Once this is done, the first requests are slow while the
cache is being populated.
Anyone already created a script to generate the main elements so this
is not done by the users? Is it a good idea?
Thanks,
L.B.
Hi,
Sometimes applying a change in RT doesn’t show up instantly in the
web UI and it requires a mason cache cleaning before the apache
restart. Once this is done, the first requests are slow while the
cache is being populated.Anyone already created a script to generate the main elements so this
is not done by the users? Is it a good idea?
You can write a script that deletes obj files for which the source
have been updated.
Thanks,
L.B.
Best regards, Ruslan.
Ruslan,
Well, that would consume quite a lot of brain CPU cycles. Maybe I try
to solve a wrong problem and cleaning the mason cache with a rm -rf
/opt/rt/var/mason/* is not the good approach.
The need is simple: I (quite often) install/modify/remove extensions,
or modify RT itself in local/ and I want to make sure I’m not misled
by the mason cache. I remove all the cache and restart apache after a
modification but the first clicks are quite longs, I was wondering if
I could optimize that.
L.B.
Ruslan,
Well, that would consume quite a lot of brain CPU cycles. Maybe I try
to solve a wrong problem and cleaning the mason cache with a rm -rf
/opt/rt/var/mason/* is not the good approach.The need is simple: I (quite often) install/modify/remove extensions,
or modify RT itself in local/ and I want to make sure I’m not misled
by the mason cache. I remove all the cache and restart apache after a
modification but the first clicks are quite longs, I was wondering if
I could optimize that.
wget http://xxxx/?user=x&pass=y
Right after restart to hit RT instead of letting users to hit it.
Restart is only required when you touched libs or config.
–
L.B.
Best regards, Ruslan.