Issue 1094 - Generate update manifests on the update server

modules/updateserver/files/sitescripts

Index: modules/updateserver/files/sitescripts
===================================================================
new file mode 100644
--- /dev/null
+++ b/modules/updateserver/files/sitescripts
@@ -0,0 +1,21 @@
+[extensions]
+hg_root=/var/lib/adblockplus

[Wladimir Palant, 2014/07/25 09:50:11]

We usually keep the repositories under /opt (see discourse, notificationserver
and sitescripts) - I guess we should do it here as well for consistency.

[Felix Dahlke, 2014/07/25 10:31:15]

Based on the file system hierarchy standard, /var/lib is the best place for
application specific changing files. /opt is for applications that don't comply
with the FHS basically.

+abp_repository=%(hg_root)s/adblockplus
+abpsafari_repository=%(hg_root)s/adblockpluschrome
+abpsafari_type=safari
+abpsafari_key=%(hg_root)s/adblockplussafari.pem

[Wladimir Palant, 2014/07/25 09:50:11]

Ouch, keeping that key on the update server only for the sake of extracting the
extension ID sucks. We need to find a better solution for this.

I guess that a long-term solution will be a build server to produce releases.
That one could store the relevant metadata for each release in some location
where the update server can look it up. This will also make it unnecessary to
sync the repositories on the update server.

[Felix Dahlke, 2014/07/25 10:31:15]

Yes, I believe that's the best approach. For now we can live with this how it is
I suppose.

+abpandroid_repository=%(hg_root)s/adblockplusandroid
+abpandroid_type=android
+ehh_repository=%(hg_root)s/elemhidehelper
+watcher_repository=%(hg_root)s/abpwatcher
+customization_repository=%(hg_root)s/abpcustomization
+urlfixer_repository=%(hg_root)s/urlfixer
+downloadsrepo=%(hg_root)s/downloads
+downloadsurl=https://downloads.adblockplus.org/
+web_root=/var/www/update
+geckoUpdateManifestPath=%(web_root)s/adblockplus/update.rdf

[Wladimir Palant, 2014/07/25 09:50:11]

That's a rather misleading path given that this file will be used for multiple
extensions including URL Fixer. Maybe /firefox/update.rdf?

We could also create individual update manifests for the extensions, that would
require more changes to the scripts however.

[Felix Dahlke, 2014/07/25 10:31:15]

Went even further and called the thing "gecko". But yeah, I guess it makes sense
to split this up, filed a follow-up for that:

https://issues.adblockplus.org/ticket/1142

[Wladimir Palant, 2014/07/25 11:11:02]

Note that splitting up is better done before we redirect the old update
manifests, this will get pretty messy otherwise.

[Felix Dahlke, 2014/07/25 14:17:56]

Messy how? We don't need redirects for the individual update manifests if those
are going to the proper update server to begin with.

+geckoUpdateManifest=extensions/template/update.rdf
+safariUpdateManifestPath=%(web_root)s/adblockplussafari/updates.plist
+safariUpdateManifest=extensions/template/updates.plist
+androidUpdateManifestPath=%(web_root)s/adblockplusandroid/androidupdates.xml

[Wladimir Palant, 2014/07/25 09:50:11]

updates.xml please - it was only called androidupdates.xml on the main server
because of another file called updates.xml.

[Felix Dahlke, 2014/07/25 10:31:15]

Done.

+androidUpdateManifest=extensions/template/androidupdates.xml