3 ms·
I know this isn't what you asked, but making your own F-Droid repo is relatively straightforward, and since your release process already cooks apks for every re
by mdaniel 5y ago
I know this isn't what you asked, but making your own F-Droid repo is relatively straightforward, and since your release process already cooks apks for every release, using the tooling to then push them into a repo would likely not be a lot of additional work, once you've gotten the underlying f-droid repo tooling setup
That process is driven by https://pypi.org/project/fdroidserver/ https://pypi.org/project/fdroidserver/ and then it just needs a local "config.py", keypair, and I use rsync --delete to publish to my repo. You can create a QR code for folks to add the repo which includes the URL and the public-key that signs items in the repo. The gory details are on their website: https://f-droid.org/docs/Setup_an_F-Droid_App_Repo/ https://f-droid.org/docs/Setup_an_F-Droid_App_Repo/ and on Mac and Linux (with Linuxbrew) you can "brew install fdroidserver" although that might not work in GitHub Actions