Hi, this seems to be a perennial issue that Heroku should just 'fix' by now.
New, very simple app, first time pushing it to Heroku.
Running: rake assets:precompile
> rake aborted!
> could not connect to server: Connection refused
> Is the server running on host "127.0.0.1" and accepting
> T
Hey,
This problem is related to the opinion that your code and the environment
it is running in are two separate things. http://12factor.net/config
The main reasoning behind this thinking is that you are then able to use
the same compiled codebase in any environment that may be thrown at it.
Ex
Neil, thanks for the theory! It's about
half over my head, but I always like that.
I don't see any refs to buildback, as I said a new, one-table app.
So I submitted a ticket. Thanks.
ed
On 3/5/2014 8:21 AM, Neil Middleton wrote:
You should use the backtrace to find the code connecting to the database.
If you manually add a database addon and promote it then deploy that is one way
to work around the connection issue.
We only provision a database for your app _after_ the first deploy.
—
Richard Schneeman
On Wed,
