6 results for tag “installation”
-
Add-ons for desktop apps
Sideloading add-ons You may want to send a user your add-on’s XPI file by some means other than a web download, such as an email distribution of a beta version for user testing. In this case, there are two practical options for installing the...
/documentation/publish/distribute-sideloading/
-
Add-ons for desktop apps
Add-ons for desktop apps Starting with Firefox 74, it is no longer be possible to have an extension be automatically installed as part of another application install. See the Add-ons Blog for more information. If you have developed an add-on to complement a desktop...
/documentation/publish/distribute-for-desktop-apps/
-
Package your extension
Package your extension During development, your extension will consist of a directory containing a manifest.json file and the other files the extension needs—scripts, icons, HTML documents, and so on. You need to zip these into a single file for uploading to AMO. Packaged extensions...
/documentation/publish/package-your-extension/
-
Distributing an add-on yourself
Distributing an add-on yourself Contents Self-distribution options You aren't required to list or distribute your add-on through addons.mozilla.org (AMO); you can distribute it yourself. However, before distributing your add-on yourself, here are some things you should consider: AMO is a very popular distribution platform,...
/documentation/publish/self-distribution/
-
Enterprise distribution
Enterprise distribution As an enterprise IT administrator, you may want to install add-ons automatically for your users. This page discusses the options. Contents Signed vs. unsigned extensionsUsing an ExtensionSettings policyBundling add-ons with a custom Firefox Signed vs. unsigned extensions All add-ons must be signed...
/documentation/enterprise/enterprise-distribution/
-
Signing and distribution overview
Signing and distributing your add-on Add-ons need to be signed before they can be installed into release and beta versions of Firefox. This signing process takes place through addons.mozilla.org (AMO), whether you choose to distribute your add-on through AMO or to do it yourself....
/documentation/publish/signing-and-distribution-overview/