Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(623)

Side by Side Diff: chrome/common/extensions/docs/templates/articles/packaging.html

Issue 11035015: Merge 159156 - Extensions Docs Server: Fix headings with no IDs (Closed) Base URL: svn://svn.chromium.org/chrome/branches/1229/src/
Patch Set: Created 8 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 <h1>Packaging</h1> 1 <h1>Packaging</h1>
2 2
3 3
4 <p> 4 <p>
5 This page describes how to package your extension. 5 This page describes how to package your extension.
6 As the <a href="overview.html">Overview</a> explains, 6 As the <a href="overview.html">Overview</a> explains,
7 extensions are packaged as signed ZIP files 7 extensions are packaged as signed ZIP files
8 with the file extension "crx"&mdash;for example, 8 with the file extension "crx"&mdash;for example,
9 <code>myextension.crx</code>. 9 <code>myextension.crx</code>.
10 </p> 10 </p>
(...skipping 13 matching lines...) Expand all
24 24
25 <p> 25 <p>
26 When you package an extension, 26 When you package an extension,
27 the extension is assigned a unique key pair. 27 the extension is assigned a unique key pair.
28 The extension's ID is based on a hash of the public key. 28 The extension's ID is based on a hash of the public key.
29 The private key is kept private 29 The private key is kept private
30 and used to sign each version of the extension. 30 and used to sign each version of the extension.
31 </p> 31 </p>
32 32
33 33
34 <h2>Creating a package</h2> 34 <h2 id="creating">Creating a package</h2>
35 35
36 <p>To package an extension:</p> 36 <p>To package an extension:</p>
37 <ol> 37 <ol>
38 <li> 38 <li>
39 Bring up the Extensions management page 39 Bring up the Extensions management page
40 by going to this URL: 40 by going to this URL:
41 <blockquote> 41 <blockquote>
42 <b>chrome://extensions</b> 42 <b>chrome://extensions</b>
43 </blockquote> 43 </blockquote>
44 </li> 44 </li>
(...skipping 113 matching lines...) Expand 10 before | Expand all | Expand 10 after
158 <li> Rename the private key that was generated 158 <li> Rename the private key that was generated
159 when you created the <code>.crx</code> file to <code>key.pem</code>. </li> 159 when you created the <code>.crx</code> file to <code>key.pem</code>. </li>
160 <li> Put <code>key.pem</code> in the top directory 160 <li> Put <code>key.pem</code> in the top directory
161 of your extension. </li> 161 of your extension. </li>
162 <li> Compress that directory into a ZIP file. </li> 162 <li> Compress that directory into a ZIP file. </li>
163 <li> Upload the ZIP file using the 163 <li> Upload the ZIP file using the
164 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Deve loper Dashboard</a>. </li> 164 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Deve loper Dashboard</a>. </li>
165 </ol> 165 </ol>
166 166
167 167
168 <h2>Packaging at the command line</h2> 168 <h2 id="packaging">Packaging at the command line</h2>
169 169
170 <p> 170 <p>
171 Another way to package extensions 171 Another way to package extensions
172 is by invoking <code>chrome.exe</code> at the command line. 172 is by invoking <code>chrome.exe</code> at the command line.
173 Use the <code>--pack-extension</code> flag 173 Use the <code>--pack-extension</code> flag
174 to specify the location of the extension's folder. 174 to specify the location of the extension's folder.
175 Use <code>--pack-extension-key</code> 175 Use <code>--pack-extension-key</code>
176 to specify the location of the extension's private key file. 176 to specify the location of the extension's private key file.
177 For example: 177 For example:
178 </p> 178 </p>
179 179
180 <pre> 180 <pre>
181 chrome.exe --pack-extension=c:\myext --pack-extension-key=c:\myext.pem 181 chrome.exe --pack-extension=c:\myext --pack-extension-key=c:\myext.pem
182 </pre> 182 </pre>
183 183
184 <p> 184 <p>
185 To suppress the dialog, 185 To suppress the dialog,
186 add <code>--no-message-box</code> to the command. 186 add <code>--no-message-box</code> to the command.
187 </p> 187 </p>
188 188
189 <h2>Package format and scripts</h2> 189 <h2 id="format">Package format and scripts</h2>
190 <p> 190 <p>
191 For more information on the format, as well as pointers to scripts you can use 191 For more information on the format, as well as pointers to scripts you can use
192 to create <code>.crx</code> files, see <a href="crx.html">CRX Package Format</a> . 192 to create <code>.crx</code> files, see <a href="crx.html">CRX Package Format</a> .
193 </p> 193 </p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698