Next: Building Applications, Previous: Setup, Up: Top [Contents][Index]
If you want to maintain a simple repository hosting only binary APKs obtained and compiled elsewhere, the process is quite simple:
config.py
, by copying the config.sample.py
from the server
project and editing it.
repo
and put APK files in it.
fdroid update
.
metadata
directory and run it again.
fdroid update
with the -c
option. It will create ’skeleton’ metadata files that are missing, and you can
then just edit them and fill in the details.
fdroid update
again.
fdroid update
adds an Icons directory into the repo directory,
and also creates the repository index (index.xml, and also index.jar if you’ve
configured the system to use a signed index).
repo
directory to your web server.
Following the above process will result in a repo
directory, which you
simply need to push to any HTTP (or preferably HTTPS) server to make it
accessible.
While some information about the applications (and versions thereof) is
retrieved directly from the APK files, most comes from the corresponding file
in the metadata
directory. The metadata file covering ALL versions of a
particular application is named package.id.txt
where package.id is the
unique identifier for that package.
See the Metadata chapter for details of what goes in the metadata file. All
fields are relevant for binary APKs, EXCEPT for Build:
entries, which
should be omitted.
Next: Building Applications, Previous: Setup, Up: Top [Contents][Index]