3 # Copy this file to config.py, then amend the settings below according to
4 # your system configuration.
6 # Custom path to the Android SDK, defaults to $ANDROID_HOME
7 # sdk_path = "$ANDROID_HOME"
9 # Custom paths to various versions of the Android NDK, defaults to 'r12b' set
10 # to $ANDROID_NDK. Most users will have the latest at $ANDROID_NDK, which is
11 # used by default. If a version is missing or assigned to None, it is assumed
17 # 'r12b': "$ANDROID_NDK",
22 # Path to the Qt SDK. It is of the form "/path/to/Qt5.7.0/5.7"
26 # '1.8': "/usr/lib/jvm/java-8-openjdk",
29 # Build tools version to be used
30 # build_tools = "25.0.2"
32 # Force all build to use the above version of build -tools, good for testing
33 # builds without having all of the possible build-tools installed.
34 # force_build_tools = True
36 # Command or path to binary for running Ant
39 # Command or path to binary for running maven 3
42 # Command or path to binary for running Gradle
45 # Set the maximum age (in days) of an index that a client should accept from
46 # this repo. Setting it to 0 or not setting it at all disables this
47 # functionality. If you do set this to a non-zero value, you need to ensure
48 # that your index is updated much more frequently than the specified interval.
49 # The same policy is applied to the archive repo, if there is one.
52 repo_url = "https://MyFirstFDroidRepo.org/fdroid/repo"
53 repo_name = "My First F-Droid Repo Demo"
54 repo_icon = "fdroid-icon.png"
55 repo_description = """
56 This is a repository of apps to be used with F-Droid. Applications in this
57 repository are either official binaries built by the original application
58 developers, or are binaries built from source by the admin of f-droid.org
59 using the tools on https://gitlab.com/u/fdroid.
62 # As above, but for the archive repo.
63 # archive_older sets the number of versions kept in the main repo, with all
64 # older ones going to the archive. Set it to 0, and there will be no archive
65 # repository, and no need to define the other archive_ values.
67 archive_url = "https://f-droid.org/archive"
68 archive_name = "My First F-Droid Archive Demo"
69 archive_icon = "fdroid-icon.png"
70 archive_description = """
71 The repository of older versions of applications from the main demo repository.
74 # This allows a specific kind of insecure APK to be included in the
75 # 'repo' section. Since April 2017, APK signatures that use MD5 are
76 # no longer considered valid, jarsigner and apksigner will return an
77 # error when verifying. `fdroid update` will move APKs with these
78 # disabled signatures to the archive. This option stops that
79 # behavior, and lets those APKs stay part of 'repo'.
81 # allow_disabled_algorithms = True
83 # Normally, all apps are collected into a single app repository, like on
84 # https://f-droid.org. For certain situations, it is better to make a repo
85 # that is made up of APKs only from a single app. For example, an automated
86 # build server that publishes nightly builds.
87 # per_app_repos = True
89 # `fdroid update` will create a link to the current version of a given app.
90 # This provides a static path to the current APK. To disable the creation of
91 # this link, uncomment this:
92 # make_current_version_link = False
94 # By default, the "current version" link will be based on the "Name" of the
95 # app from the metadata. You can change it to use a different field from the
97 # current_version_name_source = 'packageName'
99 # Optionally, override home directory for gpg
100 # gpghome = '/home/fdroid/somewhere/else/.gnupg'
102 # The ID of a GPG key for making detached signatures for apks. Optional.
103 # gpgkey = '1DBA2E89'
105 # The key (from the keystore defined below) to be used for signing the
106 # repository itself. This is the same name you would give to keytool or
107 # jarsigner using -alias. (Not needed in an unsigned repository).
108 # repo_keyalias = "fdroidrepo"
110 # Optionally, the public key for the key defined by repo_keyalias above can
111 # be specified here. There is no need to do this, as the public key can and
112 # will be retrieved from the keystore when needed. However, specifying it
113 # manually can allow some processing to take place without access to the
115 # repo_pubkey = "..."
117 # The keystore to use for release keys when building. This needs to be
118 # somewhere safe and secure, and backed up! The best way to manage these
119 # sensitive keys is to use a "smartcard" (aka Hardware Security Module). To
120 # configure F-Droid to use a smartcard, set the keystore file using the keyword
121 # "NONE" (i.e. keystore = "NONE"). That makes Java find the keystore on the
122 # smartcard based on 'smartcardoptions' below.
123 # keystore = "~/.local/share/fdroidserver/keystore.jks"
125 # You should not need to change these at all, unless you have a very
126 # customized setup for using smartcards in Java with keytool/jarsigner
127 # smartcardoptions = "-storetype PKCS11 -providerName SunPKCS11-OpenSC \
128 # -providerClass sun.security.pkcs11.SunPKCS11 \
129 # -providerArg opensc-fdroid.cfg"
131 # The password for the keystore (at least 6 characters). If this password is
132 # different than the keypass below, it can be OK to store the password in this
133 # file for real use. But in general, sensitive passwords should not be stored
135 # keystorepass = "password1"
137 # The password for keys - the same is used for each auto-generated key as well
138 # as for the repository key. You should not normally store this password in a
139 # file since it is a sensitive password.
140 # keypass = "password2"
142 # The distinguished name used for all keys.
143 # keydname = "CN=Birdman, OU=Cell, O=Alcatraz, L=Alcatraz, S=California, C=US"
145 # Use this to override the auto-generated key aliases with specific ones
146 # for particular applications. Normally, just leave it empty.
148 # keyaliases['com.example.app'] = 'example'
149 # You can also force an app to use the same key alias as another one, using
151 # keyaliases['com.example.another.plugin'] = '@com.example.another'
154 # The full path to the root of the repository. It must be specified in
155 # rsync/ssh format for a remote host/path. This is used for syncing a locally
156 # generated repo to the server that is it hosted on. It must end in the
157 # standard public repo name of "/fdroid", but can be in up to three levels of
158 # sub-directories (i.e. /var/www/packagerepos/fdroid). You can include
159 # multiple servers to sync to by wrapping the whole thing in {} or [], and
160 # including the serverwebroot strings in a comma-separated list.
162 # serverwebroot = 'user@example:/var/www/fdroid'
164 # 'foo.com:/usr/share/nginx/www/fdroid',
165 # 'bar.info:/var/www/fdroid',
168 # The full URL to a git remote repository. You can include
169 # multiple servers to mirror to by wrapping the whole thing in {} or [], and
170 # including the servergitmirrors strings in a comma-separated list.
171 # Servers listed here will also be automatically inserted in the mirrors list.
173 # servergitmirrors = 'https://github.com/user/repo'
174 # servergitmirrors = {
175 # 'https://github.com/user/repo',
176 # 'https://gitlab.com/user/repo',
179 # Any mirrors of this repo, for example all of the servers declared in
180 # serverwebroot and all the servers declared in servergitmirrors,
181 # will automatically be used by the client. If one
182 # mirror is not working, then the client will try another. If the
183 # client has Tor enabled, then the client will prefer mirrors with
184 # .onion addresses. This base URL will be used for both the main repo
185 # and the archive, if it is enabled. So these URLs should end in the
186 # 'fdroid' base of the F-Droid part of the web server like serverwebroot.
189 # 'https://foo.bar/fdroid',
190 # 'http://foobarfoobarfoobar.onion/fdroid',
193 # optionally specify which identity file to use when using rsync or git over SSH
195 # identity_file = '~/.ssh/fdroid_id_rsa'
198 # If you are running the repo signing process on a completely offline machine,
199 # which provides the best security, then you can specify a folder to sync the
200 # repo to when running `fdroid server update`. This is most likely going to
201 # be a USB thumb drive, SD Card, or some other kind of removable media. Make
202 # sure it is mounted before running `fdroid server update`. Using the
203 # standard folder called 'fdroid' as the specified folder is recommended, like
204 # with serverwebroot.
206 # local_copy_dir = '/media/MyUSBThumbDrive/fdroid'
209 # If you are using local_copy_dir on an offline build/signing server, once the
210 # thumb drive has been plugged into the online machine, it will need to be
211 # synced to the copy on the online machine. To make that happen
212 # automatically, set sync_from_local_copy_dir to True:
214 # sync_from_local_copy_dir = True
217 # To upload the repo to an Amazon S3 bucket using `fdroid server update`.
218 # Warning, this deletes and recreates the whole fdroid/ directory each
219 # time. This is based on apache-libcloud, which supports basically all cloud
220 # storage services, so it should be easy to port the fdroid server tools to
223 # awsbucket = 'myawsfdroid'
224 # awsaccesskeyid = 'SEE0CHAITHEIMAUR2USA'
225 # awssecretkey = 'yourverysecretkeywordpassphraserighthere'
228 # If you want to force 'fdroid server' to use a non-standard serverwebroot
230 # nonstandardwebroot = False
233 # If you want to upload the release apk file to androidobservatory.org
235 # androidobservatory = False
238 # If you want to upload the release apk file to virustotal.com
239 # You have to enter your profile apikey to enable the upload.
241 # virustotal_apikey = "virustotal_apikey"
244 # The build logs can be posted to a mediawiki instance, like on f-droid.org.
245 # wiki_protocol = "http"
246 # wiki_server = "server"
247 # wiki_path = "/wiki/"
248 # wiki_user = "login"
249 # wiki_password = "1234"
251 # Keep a log of all generated index files in a git repo to provide a
252 # "binary transparency" log for anyone to check the history of the
253 # binaries that are published. This is in the form of a "git remote",
254 # which this machine where `fdroid update` is run has already been
255 # configured to allow push access (e.g. ssh key, username/password, etc)
256 # binary_transparency_remote = "git@gitlab.com:fdroid/binary-transparency-log.git"
258 # Only set this to true when running a repository where you want to generate
259 # stats, and only then on the master build servers, not a development
260 # machine. If you want to keep the "added" and "last updated" dates for each
261 # app and APK in your repo, then you should enable this.
262 # update_stats = True
264 # When used with stats, this is a list of IP addresses that are ignored for
265 # calculation purposes.
268 # Server stats logs are retrieved from. Required when update_stats is True.
269 # stats_server = "example.com"
271 # User stats logs are retrieved from. Required when update_stats is True.
274 # Use the following to push stats to a Carbon instance:
275 # stats_to_carbon = False
276 # carbon_host = '0.0.0.0'
279 # Set this to true to always use a build server. This saves specifying the
280 # --server option on dedicated secure build server hosts.
281 # build_server_always = True
283 # By default, fdroid will use YAML .yml and the custom .txt metadata formats. It
284 # is also possible to have metadata in JSON by adding 'json'.
285 # accepted_formats = ('txt', 'yml')
287 # Limit in number of characters that fields can take up
288 # Only the fields listed here are supported, defaults shown
291 # 'Description': 4000,
294 # It is possible for the server operator to specify lists of apps that
295 # must be installed or uninstalled on the client (aka "push installs).
296 # If the user has opted in, or the device is already setup to respond
297 # to these requests, then F-Droid will automatically install/uninstall
298 # the packageNames listed. This is protected by the same signing key
299 # as the app index metadata.
302 # 'at.bitfire.davdroid',
308 # 'com.facebook.orca',
309 # 'com.android.vending',