Geek Answers Handbook

Trying to create a heroic production site - Resource Not Found,

I am working on an existing rails project that is deployed on a hero. I am trying to create an intermediate server that is being deployed from an intermediate branch. (the master is currently deploying for production).

I follow this page http://devcenter.heroku.com/articles/multiple-environments#starting_with_a_production_app

and I'm in the “Starting with a production application” section. The code he gives is

heroku create --stack [production stack] --remote staging --addons newrelic:bronze,logging:expanded

I am trying to adapt this to my own needs, but getting the message back Resource not found .

That's what I get for "heroku apps"

 custom_domains:basic exceptional:basic logging:expanded shared-database:5mb

If I make a heroku list , I get this

 buddystef <project manager email> vivid-window-286 vivid-earth-537

where "buddystef" is the production version of the application. So I'm trying to do this:

heroku create --stack [buddystef stack] --remote buddy-staging --addons custom_domains:basic,exceptional:basic,logging:expanded,shared-database:5mb

And I get Resource not found

Do I need to first create a separate git repository for the intermediate branch? If so, what is the best way to do this?

Grateful for any advice - max

EDIT - The message "Resource not found" seems (after googling) to be associated with logging in with incorrect credentials. But I log in as the owner of the buddystef project.

+4
source share
3 answers

It seems like you're making things too complicated, Max. Keep it simple, create an application, as John suggests, add add-ons, and then declare it an intermediate environment:

 heroku config:add RACK_ENV=staging --app stagingbuddystef

create environments/staging.rb similar to production.rb

If this is a public site, you probably want to protect it from open access, do not confuse users. See This SO Answer for Securing a Security Intermediate

Git . You must have your own intermediate branch. Remember that heroku runs on the main branch, so you must do this:

 myproj git:(staging)$ git push stagingbuddystef staging:master

Find out more about git good practices here: http://nvie.com/posts/a-successful-git-branching-model/

+3
source

Creating Heroku with synxtax stack

 heroku create test-sushi-app --stack bamboo-mri-1.9.2

where bamboo-mri-1.9.2 can be any of the following:

  • aspen-mrt-1.8.6
  • bamboo-REE-1.8.7
  • bamboo mrt-1.9.2

so I'm not sure where your [buddystef stack] coming from, but probably the problem

+1
source

I use Heroku San, which makes some of the legs for you. Github | Textbook

0
source

More articles:


All Articles