Mozdev.org allows projects to upload files to their CVS tree in a special folder called 'downloads' ([http://www.mozdev.org/source/browse/www/ example]). Files added to this folder will have the following things happen automatically:
* they will be synced to our public [http://mirrors.mozdev.org mirror system]
* extensions (files ending with .xpi) will also be handled specially if they have an [http://developer.mozilla.org/en/docs/Install_Manifests 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 [http://www.mozdev.org/projects/tags.html tag list]
* The extension will show up in the [http://www.mozdev.org/projects/applications.html applications list]
[http://www.mozdev.org/drupal/files/www/file_management.png File Management screenshot]
++++Releasing files
Once extensions (.xpi, .jar, and .zip files) are uploaded they can be "released" using our [http://www.mozdev.org/profile/file_management.html 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 [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 (//**note:** sha* hash types are necessary for secure updates//)
# 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]
++++Secure updates (using Mozdev's generated update.rdf)
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]" (#4).
++++Steps to register a file and have secure installs and updates
# 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: [http://beeblebrox.org/hashtab/ hashtab]). Your extension (if not previously shown) will show up on the application page under the [http://www.mozdev.org/projects/applications.html correct supported app].
# Login to Mozdev.org's [https://www.mozdev.org/profile/file_management.html file management] and release your new file and verify the hash (hash type is determined automatically; sha* functions are recommended).
# 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/
++++Including the update.rdf url
Mozdev does not modify your extensions so you must include the url to the update.rdf in your install.rdf before you publish it.
If you have a new extension and would like to include the link to Mozdev's generated update.rdf file in advance, use the link in the screenshot above marked #5 to upload your install.rdf and get the URL back.
Post new comment