How to host add-on source for extensions inside the enterprise?
We would like to create an add-on source site within our enterprise. If we configure the browsers to only use this source for extensions, this would allow us to control the add-ons available to our users. I have found the configuration settings in the Firefox browser to set the URL for extensions (extensions.getMoreExtensionsURL). I am unable to find any documentation on how to set up the server. Is there anything available? Has anyone else done this?
Все ответы (6)
I am open to other recommendations on how companies are controlling access to add-ons/Extensions. Input is appreciated.
Sorry I do not have a proper answer. Your proposal may help, depending on what problems you have.
That would not stop someone adding whatever they like unless you also block access to the extensions, and prevent users adding any file locally that they could then install.
- You may be better asking on the EWG mailing list about enterprise issues
- Add-ons (AMO) have their own support forum; now at
- If you are deploying customised and locked down Firefox you may find CCK useful
- https://mike.kaply.com/cck2/
- more detail see https://mike.kaply.com/tag/cck/
- Note the addon is no longer on AMO but remains free to download and use, it is only the support that has a cost. (Currently I think $500pa total, I recall someone complaining about that, yet had >10k deployments so I would have thought $500 would be peanuts )
- https://mike.kaply.com/cck2/
You could probably recreate the whole addon server if you wished then populate it with what you wish.
Thank you for the response. I am hoping that someone has first hand experience with creating a private add-on server.
It may help if others know more about your aims. For instance are you intending to host
- Just a handfull of add-ons or even only add-ons you have developed yourself
- Or are you needing a full blown server offering most of the thousands of AMO add-ons but with some specific addons or categories absent.
I imagine the first sort of scenario probably does not need much more than having the files available, or Firefox could be deployed with the add-ons. Whilst the latter scenario would probably need to mirror the AMO server.
We would like to host a reduced set of add-ons that we approve for usage within our organization. We would not want to mirror the entire AMO site. For example, we would probably not want to host even some large categories such as Themes or Search Providers. We would also not include all of the items in the Extensions category either.
From an architecture perspective, we would like to utilize the configuration settings with Firefox to point to this hosting source instead of the public source for "Get Addons" and to pull updates to Addons.
These seems like the best resources for further questions looking for first-hand experience:
John99 said
- You may be better asking on the EWG mailing list about enterprise issues
- Add-ons (AMO) have their own support forum; now at