Wouldn't it make more sense to set it in the vhost (if you're using
Passenger) or with your Mongrel config (or the like). I write app's
that live on many environments (qa, stage, prod, admin, ci, dev, test,
etc.) and have never once had an issue with RAILS_ENV.
On Oct 15, 9:58 am, Mislav Marohnić
I decided to write up a bit more of a description:
http://www.somethingunimportant.com/2009/04/06/rails-bug-found-while-streaming-output-in-actioncontroller-tests/
On Apr 5, 1:19 pm, Andrew Bloom wrote:
> I'm just trying to get people aware of my new patch. It's a very
>
I'm just trying to get people aware of my new patch. It's a very
simple update to TestProcess that allows testing of streaming output.
Before my patch TestProcess tries to build an HTML::Document with the
Proc instead of the captured output of the Proc. I've put this
together against tags/2.3.2.1,
This isn't a show stopper or a blocker, but it's really simple.
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2122-routing-with-a-blank-path_prefix-causes-a-bad-url-to-generate
Any chance we could get it accepted?
Thanks
Andrew
On Mar 9, 9:56 am, Johan Sørensen wrote:
> On
I think the fact that the private status is lost when being memoized
is misleading and confusing. Until reading this post I had no idea
that was the case and would have assumed it respected the private
keyword.
Andrew
On Mar 5, 12:53 pm, Niels Ganser wrote:
> Hi all,
>
> what do you guys think
Sent to quickly...
This patch fixes the situation where the :path_prefix is a blank
string, and simply ignores it as if it were nil.
On Mar 5, 11:52 am, Andrew Bloom wrote:
> Please see my write up
> here:http://www.somethingunimportant.com/2009/03/04/get-my-patch-added-to-...
> And
Please see my write up here:
http://www.somethingunimportant.com/2009/03/04/get-my-patch-added-to-core/
And my ticket/patch here:
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2122-routing-with-a-blank-path_prefix-causes-a-bad-url-to-generate#ticket-2122-3
Brief description:
I'm just curious why you find it to be a problem that it loads the
environment?
On Jul 2, 8:18 pm, Dave Rothlisberger <[EMAIL PROTECTED]> wrote:
> If my code tries to access the database at "compile time", e.g.
> defining methods based on values in a table, the rake db:create task
> fails:
>
>
