Message from discussion New feature: heroku.yml
Date: Sun, 2 Mar 2008 14:49:54 -0800 (PST)
Received: by 10.150.145.20 with SMTP id s20mr504524ybd.14.1204498194692; Sun,
02 Mar 2008 14:49:54 -0800 (PST)
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:184.108.40.206)
Subject: Re: New feature: heroku.yml
From: Harro <ste.ha...@gmail.com>
To: Heroku <firstname.lastname@example.org>
Content-Type: text/plain; charset=ISO-8859-1
Speaking as one of these new users, I would have to totally agree. At
the moment im in a catch 22 situation.
In order to request my application to become blessed, you ask that the
app must be complete,
however to develop the facebook application I need the app to be
blessed (for the outgoing connection).
If there was some way you could offer a limited version of this, then
heroku, in my eyes, would be perfect ;)
On Feb 26, 9:03 am, Kamilion <kamil...@gmail.com> wrote:
> Also, hard options to force the fake production mode for all users,
> sometimes your autodetection epic fails:
> production_collaborators: true
> production_public: true
> (Exceptions and Syntax Errors display as "Something has gone wrong,
> somebody's been notified")
> Some additional UI options would be helpful as well:
> display_mongrel_reset: true
> (brings back a heroku UI button somewhere to restart mongrel manually
> for us hackers who wedge it)
> That's about all I can think of for the moment.
> Defaultly off outgoing connections with throttling would satisfy many users.
> "Hey why doesn't my facebook app work" "turn on limited outgoing
> connections like this"
> Just default 'blessed' apps a higher maximum like 20 or whatever their
> current default is. This should quiet most of the new users clamoring