1
1
---
2
- # Copy this file to config.yml, then amend the settings below according to
3
- # your system configuration.
4
-
5
- # Custom path to the Android SDK, defaults to $ANDROID_HOME
6
- sdk_path : $ANDROID_HOME
7
-
8
-
9
2
10
3
# Custom paths to various versions of the Android NDK, defaults to 'r12b' set
11
4
# to $ANDROID_NDK. Most users will have the latest at $ANDROID_NDK, which is
@@ -53,46 +46,32 @@ sdk_path: $ANDROID_HOME
53
46
# The same policy is applied to the archive repo, if there is one.
54
47
# repo_maxage: 0
55
48
56
- repo_url : https://MyFirstFDroidRepo.org /fdroid/repo
57
- repo_name : My First F-Droid Repo Demo
49
+ repo_url : https://note-maps-fdroid.web.app /fdroid/repo
50
+ repo_name : Note Maps F-Droid Repo
58
51
repo_icon : fdroid-icon.png
59
52
repo_description : >-
60
53
This is a repository of apps to be used with F-Droid. Applications in this
61
54
repository are either official binaries built by the original application
62
- developers, or are binaries built from source by the admin of f-droid.org
55
+ developers, or are binaries built from source by the admin of this repo
63
56
using the tools on https://gitlab.com/u/fdroid.
64
57
65
58
# As above, but for the archive repo.
66
59
# archive_older sets the number of versions kept in the main repo, with all
67
60
# older ones going to the archive. Set it to 0, and there will be no archive
68
61
# repository, and no need to define the other archive_ values.
69
62
archive_older : 3
70
- archive_url : https://f-droid.org /archive
71
- archive_name : My First F-Droid Archive Demo
63
+ archive_url : https://note-maps-fdroid.web.app /archive
64
+ archive_name : Note Maps F-Droid Archive
72
65
archive_icon : fdroid-icon.png
73
66
archive_description : >-
74
- The repository of older versions of packages from the main demo repository.
75
-
76
- # This allows a specific kind of insecure APK to be included in the
77
- # 'repo' section. Since April 2017, APK signatures that use MD5 are
78
- # no longer considered valid, jarsigner and apksigner will return an
79
- # error when verifying. `fdroid update` will move APKs with these
80
- # disabled signatures to the archive. This option stops that
81
- # behavior, and lets those APKs stay part of 'repo'.
82
- #
83
- # allow_disabled_algorithms: true
67
+ The repository of older versions of packages from the main repository.
84
68
85
69
# Normally, all apps are collected into a single app repository, like on
86
70
# https://f-droid.org. For certain situations, it is better to make a repo
87
71
# that is made up of APKs only from a single app. For example, an automated
88
72
# build server that publishes nightly builds.
89
73
# per_app_repos: true
90
74
91
- # `fdroid update` will create a link to the current version of a given app.
92
- # This provides a static path to the current APK. To disable the creation of
93
- # this link, uncomment this:
94
- # make_current_version_link: false
95
-
96
75
# By default, the "current version" link will be based on the "Name" of the
97
76
# app from the metadata. You can change it to use a different field from the
98
77
# metadata here:
@@ -109,8 +88,6 @@ archive_description: >-
109
88
# jarsigner using -alias. (Not needed in an unsigned repository).
110
89
repo_keyalias : 428878f9f82c
111
90
112
-
113
-
114
91
# Optionally, the public key for the key defined by repo_keyalias above can
115
92
# be specified here. There is no need to do this, as the public key can and
116
93
# will be retrieved from the keystore when needed. However, specifying it
@@ -126,8 +103,6 @@ repo_keyalias: 428878f9f82c
126
103
# smartcard based on 'smartcardoptions' below.
127
104
keystore : keystore.p12
128
105
129
-
130
-
131
106
# You should not need to change these at all, unless you have a very
132
107
# customized setup for using smartcards in Java with keytool/jarsigner
133
108
# smartcardoptions: |
@@ -141,20 +116,14 @@ keystore: keystore.p12
141
116
# in text files!
142
117
keystorepass : B6D15jRojhRoJexnUj+U3BHK2y+7Wm3kRtx/PGvYmkQ=
143
118
144
-
145
-
146
119
# The password for keys - the same is used for each auto-generated key as well
147
120
# as for the repository key. You should not normally store this password in a
148
121
# file since it is a sensitive password.
149
122
keypass : B6D15jRojhRoJexnUj+U3BHK2y+7Wm3kRtx/PGvYmkQ=
150
123
151
-
152
-
153
124
# The distinguished name used for all keys.
154
125
keydname : CN=428878f9f82c, OU=F-Droid
155
126
156
-
157
-
158
127
# Use this to override the auto-generated key aliases with specific ones
159
128
# for particular applications. Normally, just leave it empty.
160
129
#
@@ -181,7 +150,6 @@ keydname: CN=428878f9f82c, OU=F-Droid
181
150
# - foo.com:/usr/share/nginx/www/fdroid
182
151
# - bar.info:/var/www/fdroid
183
152
184
-
185
153
# When running fdroid processes on a remote server, it is possible to
186
154
# publish extra information about the status. Each fdroid sub-command
187
155
# can create repo/status/running.json when it starts, then a
@@ -227,7 +195,6 @@ keydname: CN=428878f9f82c, OU=F-Droid
227
195
#
228
196
# identity_file: ~/.ssh/fdroid_id_rsa
229
197
230
-
231
198
# If you are running the repo signing process on a completely offline machine,
232
199
# which provides the best security, then you can specify a folder to sync the
233
200
# repo to when running `fdroid deploy`. This is most likely going to
@@ -238,15 +205,13 @@ keydname: CN=428878f9f82c, OU=F-Droid
238
205
#
239
206
# local_copy_dir: /media/MyUSBThumbDrive/fdroid
240
207
241
-
242
208
# If you are using local_copy_dir on an offline build/signing server, once the
243
209
# thumb drive has been plugged into the online machine, it will need to be
244
210
# synced to the copy on the online machine. To make that happen
245
211
# automatically, set sync_from_local_copy_dir to True:
246
212
#
247
213
# sync_from_local_copy_dir: true
248
214
249
-
250
215
# To upload the repo to an Amazon S3 bucket using `fdroid server
251
216
# update`. Warning, this deletes and recreates the whole fdroid/
252
217
# directory each time. This prefers s3cmd, but can also use
@@ -260,20 +225,17 @@ keydname: CN=428878f9f82c, OU=F-Droid
260
225
# awsaccesskeyid: SEE0CHAITHEIMAUR2USA
261
226
# awssecretkey: {env: awssecretkey}
262
227
263
-
264
228
# If you want to force 'fdroid server' to use a non-standard serverwebroot.
265
229
# This will allow you to have 'serverwebroot' entries which do not end in
266
230
# '/fdroid'. (Please note that some client features expect repository URLs
267
231
# to end in '/fdroid/repo'.)
268
232
#
269
233
# nonstandardwebroot: false
270
234
271
-
272
235
# If you want to upload the release apk file to androidobservatory.org
273
236
#
274
237
# androidobservatory: false
275
238
276
-
277
239
# If you want to upload the release apk file to virustotal.com
278
240
# You have to enter your profile apikey to enable the upload.
279
241
#
@@ -283,7 +245,6 @@ keydname: CN=428878f9f82c, OU=F-Droid
283
245
#
284
246
# virustotal_apikey: {env: virustotal_apikey}
285
247
286
-
287
248
# The build logs can be posted to a mediawiki instance, like on f-droid.org.
288
249
# wiki_protocol: http
289
250
# wiki_server: server
0 commit comments