neeto-deploy.json

The neeto-deploy.json file includes information related to how our application is deployed. It includes the following:

• stack

  This specifies which cloud native buildpacks stack is being used during the build and in the resulting app image. We are currently using heroku's stack and this can either be heroku-20 or heroku-22.

• env

  "env": {
    "RACK_ENV": {
      "value": "neetodeploy"
    },
    "RAILS_ENV": {
      "value": "neetodeploy"
    }
  }

• addons

  You can specify an array of addons that you need to provision along with your application dynos.

  Currently we have support for PostgreSQL, Redis and Elasticsearch. You can provision these addons like so:

  "addons": [
    {
      "plan": "heroku-postgresql",
      "options": {
        "version": "14"
      }
    },
    {
      "plan": "heroku-redis:hobby-dev"
    },
    {
      "plan": "bonsai:sandbox-6"
    }
  ],

  The plan names for the addons are as follows:

  • PostgreSQL - heroku-postgresql

  • Redis - heroku-redis:hobby-dev

  • Elasticsearch - bonsai:sandbox-6

• buildpacks

  Buildpacks are what we use to build docker images of our applications without the need of a Dockerfile.

  We need to mention the list of buildpacks that are required to build our application. In the case of Rails + React apps, we need the heroku/nodejs and heroku/ruby buildpacks. Keep in mind that the order in which we defined the buildpacks matter since it will be in this order the buildpacks would be loaded when building the image.

  Note that you can also add, delete or reorder buildpacks from the neetoDeploy project page.

• name (optional)
  A name to identify the template