heroku.yml

# The Heroku Manifest. This file defines the app in terms of Heroku resources.
#
# In this app, the deployment is done using Docker to generate the image that
# dynos (containers) will use to run.
# See https://devcenter.heroku.com/articles/docker-builds-heroku-yml

# Setup Phase: Will make sure all the necessary addons are in place.
# See https://devcenter.heroku.com/articles/docker-builds-heroku-yml#setup-defining-your-app-s-environment
setup:
  addons:
  - plan: heroku-postgresql
    as: DATABASE

  config: &main_config
    LANG: en_US.UTF-8
    RAILS_ENV: production
    RACK_ENV: production
    RAILS_LOG_TO_STDOUT: "true"
    RAILS_SERVE_STATIC_FILES: "true"

# Build Phase: This determines the steps used to build the dynos.
# See https://devcenter.heroku.com/articles/docker-builds-heroku-yml#build-defining-your-build
build:
  docker:
    # We'll define the Dockerfile & context for the web process:
    web: Dockerfile
  config:
    <<: *main_config

# Release Phase: All the steps needed to run (i.e. rails database migrations)
# when releasing a new version.
# See https://devcenter.heroku.com/articles/docker-builds-heroku-yml#release-release-phase
release:
  command:
    - rails db:migrate
  image: web

# Run Phase: The dynos needed to run, including the commands and other details.
# See https://devcenter.heroku.com/articles/docker-builds-heroku-yml#run-defining-the-process-to-run
run:
  web: puma -t 2:25 -w 1 -e production