How to link a folder with an existing Heroku app – Dev

The best answers to the question “How to link a folder with an existing Heroku app” in the category Dev.

QUESTION:

I have an existing Rails app on GitHub and deployed on Heroku. I’m trying to set up a new development machine and have cloned the project from my GitHub repository. However, I’m confused as to how to link this folder up to Heroku. Originally, I used the heroku create command, but obviously I don’t want to do that this time since it will create another Heroku instance.

ANSWER:

The Heroku CLI has an easy shortcut for this. For an app named ‘falling-wind-1624’:

$ heroku git:remote -a falling-wind-1624
Git remote heroku added.

See https://devcenter.heroku.com/articles/git#creating-a-heroku-remote

ANSWER:

Heroku links your projects based on the heroku git remote (and a few other options, see the update below). To add your Heroku remote as a remote in your current repository, use the following command:

git remote add heroku [email protected]:project.git

where project is the name of your Heroku project (the same as the project.heroku.com subdomain). Once you’ve done so, you can use the heroku xxxx commands (assuming you have the Heroku Toolbelt installed), and can push to Heroku as usual via git push heroku master. As a shortcut, if you’re using the command line tool, you can type:

heroku git:remote -a project

where, again, project is the name of your Heroku project (thanks, Colonel Panic). You can name the Git remote anything you want by passing -r remote_name.

[Update]

As mentioned by Ben in the comments, the remote doesn’t need to be named heroku for the gem commands to work. I checked the source, and it appears it works like this:

  1. If you specify an app name via the --app option (e.g. heroku info --app myapp), it will use that app.
  2. If you specify a Git remote name via the --remote option (e.g. heroku info --remote production), it will use the app associated with that Git remote.
  3. If you specify no option and you have heroku.remote set in your Git config file, it will use the app associated with that remote (for example, to set the default remote to “production” use git config heroku.remote production in your repository, and Heroku will run git config heroku.remote to read the value of this setting)
  4. If you specify no option, the gem finds no configuration in your .git/config file, and the gem only finds one remote in your Git remotes that has “heroku.com” in the URL, it will use that remote.
  5. If none of these work, it raises an error instructing you to pass --app to your command.

ANSWER:

Two things to take care while setting up a new deployment System for old App

1. To check your app access to Heroku (especially the app)

heroku apps

it will list the apps you have access to
if you set up for the first time, you probably need to

heroku keys:add

2. Then set up your git remote

For already created Heroku app, you can easily add a remote to your local repository with the heroku git: remote command. All you need is your Heroku app’s name:

heroku git:remote -a appName

you can also rename your remotes with the git remote rename command:

git remote rename heroku heroku-dev(you desired app name)

then You can use the git remote command to confirm that a remote been set for your app

 git remote -v

ANSWER:

Don’t forget, if you are also on a machine where you haven’t set up heroku before

heroku keys:add

Or you won’t be able to push or pull to the repo.