mirror of
https://gitlab.com/fdroid/fdroidserver.git
synced 2024-10-05 18:50:09 +02:00
Tools for managing builds, indexes, updates, and deployments for F-Droid repositories.
e826938734
I wrote up the feature to automatically generate symlinks with a constant name that points to the current release version. I have it on by default, with a *config.py* option to turn it off. There is also an option to set where the symlink name comes from which defaults to app['Name'] i.e. F-Droid.apk, but can easily be set to app['id'], i.e. _org.fdroid.fdroid.apk_. I think the best place for the symlinks is in the root of the repo, so like https://f-droid.org/F-Droid.apk or https://guardianproject.info/fdroid/ChatSecure.apk For the case of the current FDroid static link https://f-droid.org/FDroid.apk it can just be a symlink to the generated one (https://f-droid.org/F-Droid.apk or https://f-droid.org/org.fdroid.fdroid.apk). Right now, this feature is all or nothing, meaning it generates symlinks for all apps in the repo, or none. I can’t think of any problems that this might cause since its only symlinks, so the amount of disk space is tiny. Also, I think it would be useful for having an easy “Download this app” button on each app’s page on the “Browse” view. As long as this button is less prominent than the “Download F-Droid” button, and it is clear that it is better to use the FDroid app than doing direct downloads. For the f-droid.org repo, the symlinks should probably be based on app['id'] to prevent name conflicts. more info here: https://f-droid.org/forums/topic/static-urls-to-current-version-of-each-app/ |
||
|---|---|---|
| .pylint-plugins | ||
| buildserver | ||
| completion | ||
| docs | ||
| examples | ||
| fdroidserver | ||
| hooks | ||
| tests | ||
| wp-fdroid | ||
| .gitignore | ||
| COPYING | ||
| fd-commit | ||
| fdroid | ||
| jenkins-build | ||
| makebuildserver | ||
| MANIFEST.in | ||
| README | ||
| setup.py | ||
F-Droid is an installable catalogue of FOSS (Free and Open Source Software)
applications for the Android platform. The client makes it easy to browse,
install, and keep track of updates on your device.
The F-Droid server tools provide various scripts and tools that are used to
maintain the main F-Droid application repository. You can use these same tools
to create your own additional or alternative repository for publishing, or to
assist in creating, testing and submitting metadata to the main repository.
For documentation, please see the docs directory.
Alternatively, visit https://f-droid.org/manual/
Installing
----------
The easiest way to install the fdroidserver tools is to use virtualenv and pip
(if you are Debian/Ubuntu/Mint/etc, you can first try installing using
`apt-get install fdroidserver`). First, make sure you have virtualenv
installed, it should be included in your OS's Python distribution or via other
mechanisms like dnf/yum/pacman/emerge/Fink/MacPorts/Brew. Then here's how to
install:
git clone https://gitlab.com/fdroid/fdroidserver.git
cd fdroidserver
virtualenv env/
. env/bin/activate
pip install -e .
python2 setup.py install