#HEROKU GIT ADD REMOTE UPDATE#

Inside each the frontend and backend subdirectories, we can update the package.json file and add commands to publish right to a Heroku remote. Since we have a React and Node/Express application, npm can be used as a tool to help publish to Heroku remotes. This step can be considered optional, but by setting this up, it will be much easier to push a new/updated version of your application to Heroku later on. Set Up a Script to the Correct Heroku Remote If you run git remote -v and do not see the remote heroku, you have to add it with the command heroku git:remote -a app-frontend. If you make a mistake with the name, you can always rename it with: heroku apps:rename new_name -app old_name In the terminal, still in the app directory, run: heroku create app-frontend -b Īgain, I chose to name the app app-frontend. Similar steps will be taken for the frontend repository, but it needs to be created with a buildpack. In this instance, I renamed it to heroku-app-backend, but you can choose what to rename the remote to. Run the command git remote rename heroku heroku-app-backend. The next step would be to rename the heroku remote since we will have multiple remotes. If you run git remote -v and do not see the remote heroku, you will have to add it with the command heroku git:remote -a app-backend. You can choose to name it anything, but make sure to keep it consistent with the rest of the commands. I’m choosing to name the app on Heroku app-backend. Once there, let’s generate the Heroku back-end application with heroku create app-backend. In your command-line interface, navigate to the main app directory. We will begin by setting up the backend subdirectory. At the same time, a remote called heroku will be automatically created (you can check by typing git remote -v in the terminal). We will be using the command heroku create to create a new empty application on Heroku.

It will be assumed that the application has been pushed to GitHub with the recent changes.

#HEROKU GIT ADD REMOTE HOW TO#

This guide will cover how to deploy multiple applications under a single GitHub repository. Instead, the goal would be to deploy frontend and backend to Heroku through the app’s GitHub repository. It’s not common practice to have applications as subdirectories, and they should ideally have their own GitHub repository.Īssuming that we initialize app as the repository, deploying it to Heroku would not work. I used this approach to determine if it was possible to deploy each subdirectory to Heroku. But what if both of those were subdirectories? Let’s first examine how this structure would look: app (github repo) |_frontend (react application) |_backend (node/express application) You will most likely have separate GitHub repositories for each. Let’s say you’re working on a full-stack application where the client side is utilizing React and the server side is utilizing Node.js/Express.

Heroku git add remote