That is _great_ news!
I can banish my set all my heroku settings at once to some new state
scripts!
On Sep 4, 1:08 pm, Keenan Brock kee...@thebrocks.net wrote:
Hi GaJ
I just tested and it looks like it works the way you and I want. (it
is additive so you can just specify the one
The old thread on this is here:
http://groups.google.com/group/heroku/browse_thread/thread/7963db5d7691f52e/
Note that RACK_ENV always stayed set, in case that's what you saw.
On Sep 4, 1:08 pm, Keenan Brock kee...@thebrocks.net wrote:
Hi GaJ
I just tested and it looks like it works the
There's a couple of security issues been identified that have been
patched by Rails 2.3.4.
Question is, what's the timeline for updating the base gems? Is it
long enough that we should consider unpacking rails into our code?
--~--~-~--~~~---~--~~
You received
Hi Neil,
It's already available on Heroku. Update environment.rb, test locally
and push :)
Pedro
On Fri, Sep 4, 2009 at 1:45 AM, Neilneil.middle...@gmail.com wrote:
There's a couple of security issues been identified that have been
patched by Rails 2.3.4.
Question is, what's the timeline
Awesome, thanks for being on top of this guys!
On Sep 4, 12:24 pm, Pedro Belo pe...@heroku.com wrote:
Hi Neil,
It's already available on Heroku. Update environment.rb, test locally
and push :)
Pedro
On Fri, Sep 4, 2009 at 1:45 AM, Neilneil.middle...@gmail.com wrote:
There's a couple
Yes, we got the report about that bug and fixed sometime ago :)
Thanks guys
On Fri, Sep 4, 2009 at 6:16 AM, Keenan Brockkee...@thebrocks.net wrote:
$ heroku config
HIDE = true
RACK_ENV = production
$ heroku config:add MAINTAIN=true
Adding config vars:
MAINTAIN = true
Restarting
