| name: | URL: | QR code: |
|---|---|---|
| repo | https://warren-bank.github.io/fdroid/repo |  |
| archive | https://warren-bank.github.io/fdroid/archive |  |
- the F-Droid docs go into great detail…
- an excerpt from the page on how to: Setup an F-Droid App Repo
F-Droid.org is the default package repository (repo) in the F-Droid client, but it is not the only possibility.
Anyone can create their own repo, and users can control which repos their client is using,
including even disabling the default f-droid.org repo.
This model is modeled somewhat after the Debian GNU/Linux distro.
Like Debian and Ubuntu, you can also setup your own repos for anyone to use.
Custom repos do not even need to build the APKs, they can just be “simple binary repos” of any APKs.
- Github Pages publishes this gh-pages branch
- pro:
- it provides free static file hosting
- con:
- it doesn't provide the ability to specify server-side 301 redirects
- which is a requirement for me in choosing a host for my F-Droid app repo…
- I'd like to redirect all APK file requests to the corresponding file
within the releases section of the respective app's github repo - the alternative is to upload and mirror all binary files,
which I'm too lazy to maintain
- it doesn't provide the ability to specify server-side 301 redirects
- workaround:
- adding a CNAME configuration file to this gh-pages branch…
- allows me to easily redirect:
- from the canonical URL:
https://warren-bank.github.io/fdroid/ - to a free webhost…
- that:
- runs Apache
- includes the mod_rewrite module
- supports .htaccess with redirect rules
- currently:
- my free webhost is:
freewebhostingarea.com - my free subdomain is:
warren-bank.orgfree.com
- my free webhost is:
- that:
- from the canonical URL:
- example:
- request:
GET https://warren-bank.github.io/fdroid/repo/test.apk - response:
301 Location: http://warren-bank.orgfree.com/repo/test.apk
- request:
- allows me to easily redirect:
- example .htaccess file:
<IfModule mod_rewrite.c> RewriteEngine On </IfModule> Redirect 301 /repo/test.apk https://github.com/warren-bank/Android-ExoPlayer-AirPlay-Receiver/releases/download/v3.4.5/ExoPlayer-AirPlay-Receiver-003.04.05-16API-withAllLanguageTranslations-noDecoderExtensions-release.apk
- adding a CNAME configuration file to this gh-pages branch…
- pro:
released by original developers:
-
- tested with versions:
- IMPORTANT:
- version
0.5.7is the last version that allows HTTP redirects - the developer says:
Redirects are not supported because it makes the app more vulnerable to phishing attacks and other MitM like attacks.
- version
released by me from forks that allow HTTP redirects:
-
- tested with versions:
- IMPORTANT:
- the developer says:
We deliberately do not support redirects.
fdroidclientis not a browser, it does not implement the HTTP spec, that is far too complicated. These kinds of complications just make things much harder to run securely, and make the code a lot more complicated. Think of F-Droid's network traffic as its own custom protocol.
- the developer says:
-
- tested with versions:
- IMPORTANT:
- the developer says:
Redirects are not supported because it makes the app more vulnerable to phishing attacks and other MitM like attacks.
- the developer says:
- my fork of fdroidserver
- with a few modifications to run on Windows
- my scripts to install fdroidserver on Windows
- with a ready-to-use virtualenv
- my Node.js utility for i18n translation and HTML-entity encoding of F-Droid metadata locales