📝 docs(README): add instructions for building images in Forgejo
Some checks failed
build-and-push / docker (push) Failing after 0s

- include steps for building and pushing Docker images using Forgejo
- provide details on setting Forgejo secrets and using self-hosted runners
This commit is contained in:
nocci 2025-12-29 14:33:14 +00:00
parent a21dced86e
commit 6f778d71ac

View file

@ -31,6 +31,14 @@ _This currently gives you a captcha challenge for epic-games. Until [issue #183]
This will run `node epic-games; node prime-gaming; node gog` - if you only want to claim games for one of the stores, you can override the default command by appending e.g. `node epic-games` at the end of the `docker run` command, or if you want several `bash -c "node epic-games.js; node gog.js"`. This will run `node epic-games; node prime-gaming; node gog` - if you only want to claim games for one of the stores, you can override the default command by appending e.g. `node epic-games` at the end of the `docker run` command, or if you want several `bash -c "node epic-games.js; node gog.js"`.
Data (including json files with claimed games, codes to redeem, screenshots) is stored in the Docker volume `fgc`. Data (including json files with claimed games, codes to redeem, screenshots) is stored in the Docker volume `fgc`.
### Eigene Images aus Forgejo bauen
Falls du den Fork in einer selbst gehosteten Forgejo-Instanz pflegst:
- Der Workflow `.forgejo/workflows/build.yml` baut/pusht das Docker-Image auf `push` nach `main`.
- Setze in Forgejo die Secrets `REGISTRY`, `REGISTRY_IMAGE`, `REG_USER`, `REG_TOKEN` (PAT mit Paket-Push).
- Self-hosted Runner mit Docker muss registriert sein (`runs-on: self-hosted`).
- Danach kannst du das Image ziehen, z.B.: `docker pull $REGISTRY_IMAGE:latest`.
<details> <details>
<summary>I want to run without Docker or develop locally.</summary> <summary>I want to run without Docker or develop locally.</summary>