Home

Diff for MozdevDownloadReleases

Thu, 03/27/2008 - 02:22 by grimholtzFri, 04/11/2008 - 20:05 by silfreed

Reworded a "pulled out"

Adding info about secure update.rdf

< previous diffnext diff >
Changes to Body
Line 10 Line 10
* Mark the file as released: this allows the file to be considered for installs and updates and updates the latest version in [http://www.mozdev.org/projects/applications.html applications list] * Mark the file as released: this allows the file to be considered for installs and updates and updates the latest version in [http://www.mozdev.org/projects/applications.html applications list]
* Verify the file hash: Mozdev.org uses the file's MD5 or SHA1 hash to create secure installation links (using [http://developer.mozilla.org/en/docs/XPInstall_API_Reference:InstallTrigger_Object InstallTrigger]) and generate update.rdf files to allow secure updates with Firefox 3 * Verify the file hash: Mozdev.org uses the file's MD5 or SHA1 hash to create secure installation links (using [http://developer.mozilla.org/en/docs/XPInstall_API_Reference:InstallTrigger_Object InstallTrigger]) and generate update.rdf files to allow secure updates with Firefox 3
 +* Add an update info URL - this allows [http://developer.mozilla.org/en/docs/Toolkit_API Toolkit]-based app to display a small blurb about the update which is pulled from this URL (see: [http://developer.mozilla.org/en/docs/Extension_Versioning%2C_Update_and_Compatibility#Providing_Details_about_Updates Extension Versioning, Update and Compatibility]
 +
 +You can utilize the update.rdf file generated by Mozdev.org in order to provide secure updates by putting it place of your [http://developer.mozilla.org/en/docs/install.rdf#updateURL updateUrl]. The link to your update.rdf file will be beside the extension name in the file management tool linked as "[u]".
++++Steps to register a file and have secure installs ++++Steps to register a file and have secure installs
Revision of Fri, 04/11/2008 - 20:05:

MozdevDownloadReleases

Mozdev.org allows projects to upload files to their CVS tree in a special folder called 'downloads' (example). Files added to this folder will have the following things happen automatically:

  • they will be synced to our public mirror system
  • extensions (files ending with .xpi) will also be handled specially if they have an install manifest:
    • The extension name, description, and version will be parsed and stored in the mozdev database
    • The supported applications will be parsed from the em:targetAppliation tag
    • The project will be automatically tagged based on the supported applications (this shows up on the front page and in the tag list
    • The extension will show up in the applications list

Once extensions (.xpi, .jar, and .zip files) are uploaded they can be "released" using our file management web interface at Mozdev.org. There are two separate steps:

  • Mark the file as released: this allows the file to be considered for installs and updates and updates the latest version in applications list
  • Verify the file hash: Mozdev.org uses the file's MD5 or SHA1 hash to create secure installation links (using InstallTrigger) and generate update.rdf files to allow secure updates with Firefox 3
  • Add an update info URL - this allows Toolkit-based app to display a small blurb about the update which is pulled from this URL (see: Extension Versioning, Update and Compatibility

You can utilize the update.rdf file generated by Mozdev.org in order to provide secure updates by putting it place of your updateUrl. The link to your update.rdf file will be beside the extension name in the file management tool linked as "[u]".

Steps to register a file and have secure installs

  1. Upload an extension to your project in the downloads/ directory. Be sure to compute a sha1 or md5 hash and save it for later (windows: hashtab). Your extension (if not previously shown) will show up on the application page under the correct supported app.
  2. Login to Mozdev.org's file management and release your new file and verify the hash (md5 or sha1 is determined automatically).
  3. Browse to your project overview page (https://www.mozdev.org/projects/overview/PROJECT/) and see your extension list with the most recent version displayed and an InstallTrigger link setup. example: https://www.mozdev.org/projects/overview/www/