Does it work if you have Railo pointed at the "real" directory instead of the sym link?
I'd personally set it so that Railo is always inspecting templates for dev/staging systems and then set it in production to never inspect and instead bounce the server on a code promotion. Cleaning up memory periodically for production releases is usually a good idea, imho. Judah On Tue, Jan 8, 2013 at 1:26 PM, Zaphod Beeblebrox < [email protected]> wrote: > > It's offtopic since is CF related ;) > > Anyway, I've been using capistrano ( a ruby deployment tool) to deploy new > releases to the production server. The production server is using Railo. > > The dir structure is like so: > > app_name > app_name/releases > app_name/shared > app_name/current <- symlink to most current release > > So, capistrano uploads a new release and then symlinks it to the "current" > directory. Railo is pointed at "current" to serve the CF files from. Only > problem is that Railo doesn't recognize the change. I have to restart the > server or clear out the cache to get it to start serving the new files. > Anyone know how to programmatically clear the cache? > > My last resort is to bounce the server after a deploy. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:359787 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm
