FirefoxOS/New security model/Getting Started with Signed Packages: Difference between revisions

FirefoxOS/New security model/Getting Started with Signed Packages (view source)

Revision as of 09:34, 16 November 2015

17 bytes added , 16 November 2015

→‎Creating/Modifying a Signed Package

Hchang

Confirmed users

158

edits

@@ Line 22: / Line 22: @@
 === 1. Write a Regular Gaia App ===
-The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest. Note that system message and web activity is still not supported at the moment.
+The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest even though system message and web activity is still not supported at the moment.
-=== 2. Add Required Fields to the Manifest File ===
+=== 2. Add Additional Required Fields to the Manifest File ===
 Beside the well-known fields in the gaia manifest, there are two additional fields that you have to add to the manifest:
 # package-identifer: A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
@@ Line 40: / Line 40: @@
 ** The package is served from the location specified in the manifest (moz-package-origin)
-Then you can now use [URL-of-the-package]!//[relative-path-to-resource] to navigate the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.
+Now you can use [URL-of-the-package]!//[resource-path-relative-to-the-package] to access the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.
 <br>