radhames brito wrote:
anyway what you may be able to do is change the db connection.
How to do this?
Does it work for a single session, while other sessions work in
production mode? Is it possible to switch the current session to sandbox
mode and back?
--
Posted via
what i am afraid that will be a problem are plug ins and gems, you could add
a filter in the action controller and stuff, but i think that the plguins
and gem may not follow
On Fri, Sep 10, 2010 at 8:16 AM, Fritz Trapper li...@ruby-forum.com wrote:
radhames brito wrote:
anyway what you may be
On Fri, Sep 10, 2010 at 9:09 AM, radhames brito rbri...@gmail.com wrote:
what i am afraid that will be a problem are plug ins and gems, you could
add a filter in the action controller and stuff, but i think that the
plguins and gem may not follow
On Fri, Sep 10, 2010 at 8:16 AM, Fritz
read this , this guy had your prbblem
http://www.mail-archive.com/rubyonrails-talk@googlegroups.com/msg45941.html
On Fri, Sep 10, 2010 at 9:09 AM, radhames brito rbri...@gmail.com wrote:
On Fri, Sep 10, 2010 at 9:09 AM, radhames brito rbri...@gmail.com wrote:
what i am afraid that will be a
Fritz Trapper wrote:
I would like to give my users an opportunity to switch the application
into a sandboxmode, where it is possible to play with it without the
danger to insert junk into the database.
I guess, setting RAILS_ENV = 'development' works globally for the whole
server. Is there
Marnen Laibow-Koser wrote:
I don't think you want to do that. I think you want to create a clone
of your *production* environment (call it sandbox or something) with a
separate database, then have a completely separate instance of the
application running with RAILS_ENV set to 'sandbox'.
6 matches
Mail list logo
