Skip to content

Heroku API Key and Forking #1

@idkjs

Description

@idkjs

TL;DR: Make a note to walkthrough users that they will have to add their Heroku API Key to CircleCI before starting or the first error wont look like the walkthrough. You will get this:

if [ "${CIRCLE_BRANCH}" == "master" ]; then
  git push heroku master
  heroku run python manage.py deploy
  heroku restart
fi
Shell: /bin/bash -eo pipefail

Username for 'https://git.heroku.com': fatal: could not read Username for 'https://git.heroku.com': No such file or directory
Exited with code 128

Adding the key will get you the expected first error.

Also: When forking, make sure to change project name to not conflict on Heroku with the tutorial instance which has the 'cci-demo-walkthrough' namespace occupied.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions