pokeapi-api-data/updater
Alessandro Pezzè 93c0e5a74b
Use venv (#261)
2024-10-16 03:47:14 +02:00
..
cmd.bash Use venv (#261) 2024-10-16 03:47:14 +02:00
Dockerfile cicd: remove openssh 2024-01-08 12:43:23 +01:00
LICENSE Add docs 2018-09-15 01:51:34 -07:00
README.md #201 continuation (#202) 2023-12-13 08:24:16 +01:00
Run-Updater.ps1 feat: add Windows support 2020-02-24 00:05:56 +01:00

Updater Bot

Docker Repository on Quay

Usage

First, make sure you can read/write the target repository over SSH. Launch the bot with a volume containing the SSH keys to /root/.ssh and an environment variable for email address. Since this container runs Docker within itself, it needs to run in privileged mode.

docker network create pokeapi
docker run --privileged --network pokeapi --network-alias docker -v ~/.ssh:/root/.ssh -e COMMIT_EMAIL=example@example.com quay.io/pokeapi/updater

Check the log for failed clones, sometimes Magikarp times out.

Environment Variables

Required

  • COMMIT_EMAIL

Optional

See the Dockerfile for the defaults.

  • COMMIT_NAME
  • COMMIT_MESSAGE
  • BRANCH_NAME
  • REPO_POKEAPI
  • REPO_DATA

Build Docker image

docker build -t pokeapi-updater .

Run on Windows

Your public/private keys with KeyName name will be shared with the pokeapi-updater container. Be sure those keys are the ones with write access on https://github.com/PokeAPI/pokeapi

pwsh Run-Updater.ps1 -KeyName id_rsa -CommitterEmail example@example.com