- Be aware of URL on the manifest
- Make a web.config file
First lets start with the manifest, specifically the field: url. Assuming your web site is on another address different that the one on Azure, the url field on the manifest file must be:
“url”: “http://name_of_you_azure_website.azurewebsites.net/”
Second -and the most important one-, refers to serving that manifest. Mozilla’s website is well documented regarding on how to serve the manifest.webapp under Apache or NGINX, however there’s no mention on how to do it with IIS. Fortunately, the procedure to accomplish it, is fairly straightforward. In short, you need to create a plain text file called web.config, which must reside on the same directory where you manifest is, and for that matter, your whole website.
The web.config must include the following:
<configuration>
<system.webServer>
<staticContent>
<mimeMap fileExtension=”.webapp” mimeType=”application/x-web-app-manifest+json” />
</staticContent>
</system.webServer>
</configuration>
That’s it! You’re set to host your web app, now you need to pass it through the validator, then submit it to the FireFox marketplace and wait for iy to be release to the public.