Skip to content

Commit

Permalink
Save heroku email as secret instead of main.yml
Browse files Browse the repository at this point in the history
  • Loading branch information
Torom committed May 3, 2022
1 parent d92e2c8 commit 16a86a8
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
5 changes: 2 additions & 3 deletions .github/workflows/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,11 +10,10 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: akhileshns/heroku-deploy@v3.12.12 # This is the action
- uses: akhileshns/heroku-deploy@v3.12.12
with:
heroku_api_key: ${{secrets.HEROKU_API_KEY}}
heroku_email: ${{secrets.HEROKU_EMAIL}}
heroku_app_name: "APPNAME" # Insert your Heroku app name here.
heroku_email: "YOUR EMAIL" # Insert your Heroku email here.
usedocker: true
docker_heroku_process_type: "worker"

3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -141,9 +141,10 @@ The account **cannot have played any game** before becoming a Bot account. The u
- Create a [new heroku app](https://dashboard.heroku.com/new-app).
- Go to [Account Settings](https://dashboard.heroku.com/account) on Heroku, scoll down to `API Key` and copy it.
- In your fork go to `Settings` -> `Secrets` and create a `New repository secret`. Name is `HEROKU_API_KEY` and value is the api key from Heroku.
- Create another `New repository secret`. Name is `HEROKU_EMAIL` and value is the email adress you use for Heroku.
- Go to `Settings` tab on Heroku and create a variable, set `LICHESS_BOT_TOKEN` as key and your Lichess token as value.
- Go to the `Actions` tab on your fork and enable them.
- Insert your app name and your heroku email adress into the [.github/workflows/main.yml](/.github/workflows/main.yml) of your fork and commit it.
- Insert your app name into the [.github/workflows/main.yml](/.github/workflows/main.yml) of your fork and commit it.

Now the docker container gets deployed. This may take a moment. After the successful deployment, the worker needs to be activated in the `Resources` tab on Heroku.

Expand Down

0 comments on commit 16a86a8

Please sign in to comment.