hank/BigBrainParking
1
0
Fork 0
Code Issues Pull requests Projects Releases 22 Packages Wiki Activity Actions

docs: clarify Obtainium reads repo Releases (not Packages)

Browse source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Hank 2026-07-06 08:36:26 -07:00
parent 1dede50995
commit 170f2fa63c
1 changed files with 13 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/DISTRIBUTION.md
View file

@ -60,15 +60,24 @@ new release `v0.1.0`. Done.
## 5. Add the app in Obtainium (on the phone) ## 5. Add the app in Obtainium (on the phone)
Obtainium supports Gitea/Forgejo release sources. Add app → paste: Obtainium reads **straight from the repo site** via its native Gitea/Forgejo **Releases**
source — no separate web server needed. Add app → paste:
``` ```
https://git.mowden.top/hank/BigBrainParking https://git.mowden.top/hank/BigBrainParking
``` ```
Pick the **Gitea** (or **Forgejo**) source type if prompted, and Obtainium will track Pick the **Gitea** (or **Forgejo**) source type if prompted, and Obtainium tracks releases
releases and offer each new signed APK. Install ntfy + set it as your UnifiedPush and offers each new signed APK. The repo being public means Obtainium needs no token.
distributor for push later. Install ntfy + set it as your UnifiedPush distributor for push later.
### Releases vs. Packages
Use **Releases**, not the **Packages** tab. Gitea/Forgejo *Packages* is a general artifact
registry (npm, maven, container, generic) — Obtainium has no package-registry source, so it
won't see APKs there. (You *can* upload an APK to the generic registry and point Obtainium at
a "Direct APK link," but then Obtainium can't detect new versions automatically. Releases —
where CI attaches the versioned APK — is the right mechanism.)
### Fallback if your Obtainium build lacks Gitea support ### Fallback if your Obtainium build lacks Gitea support