On Tue, Oct 13, 2009 at 9:53 AM, Mislav Marohnić
wrote:
> The default value for RAILS_ENV is set to "development" in initializer.rb,
> which is loaded right after boot.rb has determined the boot strategy.
> I created a "config/preinitializer.rb" which was supposed to provide another
> default val
/sqliteTest 613 > script/about
About your application's environment
Ruby version 1.9.1 (powerpc-darwin9.8.0)
RubyGems version 1.3.5
Rack version 1.0
Rails version 2.3.4
Active Record version 2.3.4
Active Resource version 2.3.4
Action Mailer vers
+1 I've had similar problems.
-John
On Tue, Oct 13, 2009 at 12:53 PM, Mislav Marohnić wrote:
> The default value for RAILS_ENV is set to "development" in initializer.rb,
> which is loaded right after boot.rb has determined the boot strategy.
> I created a "config/preinitializer.rb" which was sup
The default value for RAILS_ENV is set to "development" in initializer.rb,
which is loaded right after boot.rb has determined the boot strategy.
I created a "config/preinitializer.rb" which was supposed to provide another
default value for RAILS_ENV ("staging" or "production", depending on the
host
Looks really promising - but I'm not entirely sure how you'd go about
using it.
Would you be willing to give a few examples of 'realish' tests? :)
> Please provide feedback at
> https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/3...
I don't have a login for that lighthouse -
Hi,
I have an app using AR that is threaded, and accesses multiple
databases.
Sometimes I get MySQL server has gone away errors if a connection
timed out due to a long period of inactivity.
So I would wish to verify the connections before using them.
Using verify_active_connections! is not pos
Hi,
I posted a patch to Lighthouse to enable end-to-end tests of REST APIs
and clients by coupling ActiveResource requests to Rails
IntegrationTests. Please provide feedback at
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/3368-allow-activeresource-to-use-integrationtests-
