User login
Navigation
Search
Diff for MozdevDownloadReleases
| Mon, 12/15/2008 - 16:24 by silfreed | Wed, 07/08/2009 - 13:36 by mozdev | ||
|---|---|---|---|
removing mention of md5 | adding additional sha* functions | ||
| < previous diff | |||
| Changes to Body | |||
| Line 1 | Line 1 | ||
| - | 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:
| + | <p>Mozdev.org allows projects to upload files to their CVS tree in a special folder called 'downloads' (<a href="http://www.mozdev.org/source/browse/www/">example</a>). Files added to this folder will have the following things happen automatically:</p> |
| - | * 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]:
| + | <ul> |
| - | * The extension name, description, and version will be parsed and stored in the mozdev database
| + | <li>they will be synced to our public <a href="http://mirrors.mozdev.org">mirror system</a></li> |
| - | * The supported applications will be parsed from the em:targetAppliation tag
| + | <li>extensions (files ending with .xpi) will also be handled specially if they have an <a href="http://developer.mozilla.org/en/docs/Install_Manifests">install manifest</a>:<ul> |
| - | * 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]
| + | <li>The extension name, description, and version will be parsed and stored in the mozdev database</li> |
| - | * The extension will show up in the [http://www.mozdev.org/projects/applications.html applications list]
| + | <li>The supported applications will be parsed from the em:targetAppliation tag</li> |
| - | + | <li>The project will be automatically tagged based on the supported applications (this shows up on the front page and in the <a href="http://www.mozdev.org/projects/tags.html">tag list</a></li> | |
| - | [http://www.mozdev.org/drupal/files/www/file_management.png File Management screenshot]
| + | <li>The extension will show up in the <a href="http://www.mozdev.org/projects/applications.html">applications list</a></li> |
| - | + | </ul></li> | |
| - | ++++Releasing files
| + | </ul> |
| - | 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]
| + | <p><img src="http://www.mozdev.org/drupal/files/www/file_management.png" alt="File Management screenshot" title="File Management screenshot" /></p> |
| - | # Verify the file hash: Mozdev.org uses the file's 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]
| + | |
| - | + | <h4>Releasing files</h4> | |
| - | ++++Secure updates (using Mozdev's generated update.rdf)
| + | <p>Once extensions (.xpi, .jar, and .zip files) are uploaded they can be "released" using our <a href="http://www.mozdev.org/profile/file_management.html">file management</a> web interface at Mozdev.org. There are two separate steps:</p> |
| - | 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).
| + | |
| - | + | <ol> | |
| - | ++++Steps to register a file and have secure installs and updates
| + | <li>Mark the file as released: this allows the file to be considered for installs and updates and updates the latest version in <a href="http://www.mozdev.org/projects/applications.html">applications list</a></li> |
| - | # Upload an extension to your project in the downloads/ directory. Be sure to compute a sha1 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].
| + | <li>Verify the file hash: Mozdev.org uses the file's sha1, sha256, sha384, or sha512 hash to create secure installation links (using <a href="http://developer.mozilla.org/en/docs/XPInstall_API_Reference:InstallTrigger_Object">InstallTrigger</a>) and generate update.rdf files to allow secure updates with Firefox 3 (<em><strong>note:</strong> sha* hash types are necessary for secure updates</em>)</li> |
| - | # 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).
| + | <li>Add an update info URL - this allows <a href="http://developer.mozilla.org/en/docs/Toolkit_API">Toolkit</a>-based app to display a small blurb about the update which is pulled from this URL (see: <a href="http://developer.mozilla.org/en/docs/Extension_Versioning%2C_Update_and_Compatibility#Providing_Details_about_Updates">Extension Versioning, Update and Compatibility</a></li> |
| - | # 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/
| + | </ol> |
| - | + | ||
| - | ++++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.
| + | <h4>Secure updates (using Mozdev's generated update.rdf)</h4> |
| - | 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.
| + | <p>You can utilize the update.rdf file generated by Mozdev.org in order to provide secure updates by putting it place of your <a href="http://developer.mozilla.org/en/docs/install.rdf#updateURL">updateUrl</a>. The link to your update.rdf file will be beside the extension name in the file management tool linked as "[[u]]" (#4).</p> |
| + | |||
| + | |||
| + | <h4>Steps to register a file and have secure installs and updates</h4> | ||
| + | <ol> | ||
| + | <li>Upload an extension to your project in the downloads/ directory. Be sure to compute a sha1 hash and save it for later (windows: <a href="http://beeblebrox.org/hashtab/">hashtab</a>). Your extension (if not previously shown) will show up on the application page under the <a href="http://www.mozdev.org/projects/applications.html">correct supported app</a>.</li> | ||
| + | <li>Login to Mozdev.org's <a href="https://www.mozdev.org/profile/file_management.html">file management</a> and release your new file and verify the hash (hash type is determined automatically; sha* functions are recommended).</li> | ||
| + | <li>Browse to your project overview page (<a href="https://www.mozdev.org/projects/overview/PROJECT/">https://www.mozdev.org/projects/overview/PROJECT/</a>) and see your extension list with the most recent version displayed and an InstallTrigger link setup. example: <a href="https://www.mozdev.org/projects/overview/www/">https://www.mozdev.org/projects/overview/www/</a></li> | ||
| + | </ol> | ||
| + | |||
| + | |||
| + | <h4>Including the update.rdf url</h4> | ||
| + | <p>Mozdev does not modify your extensions so you must include the url to the update.rdf in your install.rdf before you publish it.<br /> | ||
| + | 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.</p> | ||
| + | |||
Current revision:
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
Releasing files
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 sha1, sha256, sha384, or sha512 hash to create secure installation links (using 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 Toolkit-based app to display a small blurb about the update which is pulled from this URL (see: 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 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 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.
- Login to Mozdev.org's 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.