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. Exactly the same code should function in dev, staging, production, whatever without modification. Not allowing the environment in the build process ensures that you're getting these deterministic builds. Without this determinism, features such as pipelines or the release API ( https://blog.heroku.com/archives/2013/12/20/programmatically_release_code_to_heroku_using_the_platform_api) kinda suck hard, as your compiled app needs modification to run. Saying that, we're aware that some frameworks (most notably by far, Rails) has issue with this and insists on connecting to the database for doing things such as compiling static assets (why, I don't know). `user-env-compile` was an attempt to fix this, and the replacement `buildpack-env-arg` (for Ruby apps) should replace this ( https://devcenter.heroku.com/changelog-items/416). Assuming you're not using a third party buildpack, deploys of Rails apps should just work(tm) so you shouldn't see any issues. However, if you are using the Heroku buildpack (i.e not setting BUILDPACK_URL in your config), and are seeing issues, raise a ticket at help.heroku.com and the Ruby team can take a look. Neil On Wed, Mar 5, 2014 at 12:47 PM, Ed Jones <ed.jo...@gmail.com> wrote: > 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 >> TCP/IP connections on port 5432? >> > > There seem to be lots of solutions to this, or at least lots of attempts > at solutions. > > - The current 'official' solution here > > https://devcenter.heroku.com/articles/rails-asset-pipeline#troubleshootingdoesn't > even execute. > - The solution that worked in the fall has been deprecated by Heroku: > > http://stackoverflow.com/questions/16124490/heroku-rails-4-could-not-connect-to-server-connection-refused > | https://devcenter.heroku.com/articles/labs-user-env-compile > - This is RAILS 4, so the oft-cited solution to > set<http://stackoverflow.com/questions/18503073/cant-deploy-to-heroku-because-the-server-refused-the-connection>config > .assets.initialize_on_precompile = > false<http://stackoverflow.com/questions/18503073/cant-deploy-to-heroku-because-the-server-refused-the-connection>no > longer applies? > > As I said, new app from Rails composer with one table of content. First > time (for the app, not me) push to Heroku. > > Thanks, > > Ed > > -- > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Heroku Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to heroku+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
