can i have a direct URL(for self served extension) and serve the extension via mozilla ad-on website(only accessible via that direct URL and not available for users when they try to search it)
Can i get an update for a self served extension which was served from s3, via mozilla ad-on so that i won’t have to manage versions on s3?
Note :- I don’t want my extension to be accessible publicly. i should only be served to people having the direct link or something similar.
Hey @Mukul_Gaddhyan! Welcome to the Add-ons section of our Discourse server
The scenario you described is not officially supported. The intent of the self distribution option is that an add-on developer takes on the responsibility of hosting and updating the add-on to suit their needs. I don’t know if it’s technically possible for you to do what you you’ve described, but even if it is there’s no guarantee it will work tomorrow.
Hi @dotproto Thank you for your input. Can you please provide few more insights on the below points.
Given that direct Mozilla-served hosting/updates for unlisted, self-distributed add-ons aren’t officially supported, we’re exploring alternative possibilities for managing updates and installations.
update_url to AMO: For a self-distributed extension (hosted on our own servers, e.g., S3), is it possible to use the update_url key in our manifest.json to point to an AMO URL for updates? For example, could we use something like:JSON"applications": { "gecko": { "update_url": "https://addons.mozilla.org/en-US/firefox/addon/" } }or a specific extension page on AMO (if one exists even without a full listing)?
Slug for Self-Served: Is it possible to obtain a specific “slug” or identifier on AMO for a self-served extension that could be used in an update_url, even if the extension isn’t publicly listed in search results?
Eg. https://addons.mozilla.org/en-US/firefox/addon/YOUR_EXTENSION_SLUG/
Scope of “This add-on is experimental”: When submitting an add-on and marking it as “experimental,” the description mentions “reduced visibility.” Could you clarify the scope of this reduced visibility? Does it prevent the add-on from being found via search option to the public?
I am trying to explore ways to move(update) my users who have installed extension via s3(self-served) to amo, also new user installations through amo, without making my extension available for public.
