Hello, On 26 jan 2006, at 17.40, Duane Johnson wrote:
I've heard that some core members aren't too excited about adding a tmp/ folder to RAILS_ROOT, and I can understand why; however, adding the tmp/ folder (option #1) may be the best solution for a number of reasons:a) It guarantees that there will be no conflict between rails appsb) Apps can benefit from the change immediately (no need to generate a UUID with railties)c) We'll finally have a place to put those pesky fastcgi socket files d) Other plugins may benefit from a tmp/ folder, e.g. file_column?
Rails' default session storage is one of the biggest reason we at TextDrive have had to to start using an almost abnormal large /tmp partition (and upping the number of inodes it'll hold as well), due to the sheer amount of rubysess files being generated. We've even begun to recommend either moving the PStore tmpdir to RAILS_ROOT/tmp or switching to the ActiveRecordStore[1].
Granted, one could argue that that's a "hit" one has to take for offering rails hosting, but the above is just the way it looks today, and it is causing the occasional hiccup when it fills up (which will happen, even when cleaning out (really) old session files) and other daemons can't use /tmp.
And speaking as a developer, I wouldn't mind having a rails specific tmp dir under RAILS_ROOT for the same reasons Duane states, if the intention is to keep the current default session storage...
Cheers, JS [1]: http://weblog.textdrive.com/article/196/on-rails-sessions
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
