> For the complete documentation index, see [llms.txt](https://docs.netcoresaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.netcoresaas.com/getting-started/deploy/publish-to-heroku.md).

# Deploy to heroku

## Install Heroku CLI

If you haven't already, install the CLI: <https://devcenter.heroku.com/articles/heroku-cli>

## 1. Connect a heroku app

### New app

Create your app manually at dashboard.heroku.com or type:

```
heroku create your-app
```

### Existing app

If you've already created your app, connect it:

```
heroku git:remote -a your-app
```

## 2. Adding Node.js and .NET Core buildbacks

.NET Core is not officially supported on Heroku at present. Third party buildpacks are one option for extending the platform, for this project we are using: <https://elements.heroku.com/buildpacks/jincod/dotnetcore-buildpack>

```
heroku buildpacks:add heroku/nodejs
heroku buildpacks:add jincod/dotnetcore
```

### Heroku environment variables

```
heroku config:set ASPNETCORE_ENVIRONMENT=Production
```

You can change environment variables directly from the heroku app settings:

![](/files/-MFUG7LH0XMWWZ3oFNc4)

## 3. Deploy

You can directly push to the heroku repository:

```
git push heroku master
```

![Herokuapp deployed](/files/-MFUIld5wkZRPPxyWO_j)

Or better yet, go to [https://dashboard.heroku.com/apps/**YOUR-APP**/deploy/github](https://dashboard.heroku.com/apps/YOUR-APP/deploy/github) and enable **Automatic deploys** so you only deploy when you type:

```
git push origin master
```

### 4. Open your app

Open your app yourappname.herokuapp.com and ensure everything is working.

{% hint style="warning" %}
If you set your LIVE Stripe API Keys and LIVE products, keep in mind that you will be charged.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.netcoresaas.com/getting-started/deploy/publish-to-heroku.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.