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

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

Issue 7824048: Add info about providing the .pem file if you've previously (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/
Patch Set: Created 9 years, 3 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
« no previous file with comments | « no previous file | chrome/common/extensions/docs/static/packaging.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note: 1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:
2 1) The <head> information in this page is significant, should be uniform 2 1) The <head> information in this page is significant, should be uniform
3 across api docs and should be edited only with knowledge of the 3 across api docs and should be edited only with knowledge of the
4 templating mechanism. 4 templating mechanism.
5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a 5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
6 browser, it will be re-generated from the template, json schema and 6 browser, it will be re-generated from the template, json schema and
7 authored overview content. 7 authored overview content.
8 4) The <body>.innerHTML is also generated by an offline step so that this 8 4) The <body>.innerHTML is also generated by an offline step so that this
9 page may easily be indexed by search engines. 9 page may easily be indexed by search engines.
10 --><html xmlns="http://www.w3.org/1999/xhtml"><head> 10 --><html xmlns="http://www.w3.org/1999/xhtml"><head>
(...skipping 254 matching lines...) Expand 10 before | Expand all | Expand 10 after
265 </li> 265 </li>
266 </ol> 266 </ol>
267 </li><li> 267 </li><li>
268 <a href="#update">Updating a package</a> 268 <a href="#update">Updating a package</a>
269 <ol> 269 <ol>
270 <li style="display: none; "> 270 <li style="display: none; ">
271 <a>h3Name</a> 271 <a>h3Name</a>
272 </li> 272 </li>
273 </ol> 273 </ol>
274 </li><li> 274 </li><li>
275 <a href="#H2-2">Packaging at the command line</a> 275 <a href="#upload"> Uploading a previously packaged extension to th e Chrome Web Store</a>
276 <ol> 276 <ol>
277 <li style="display: none; "> 277 <li style="display: none; ">
278 <a>h3Name</a> 278 <a>h3Name</a>
279 </li> 279 </li>
280 </ol> 280 </ol>
281 </li><li> 281 </li><li>
282 <a href="#H2-3">Package format and scripts</a> 282 <a href="#H2-3">Packaging at the command line</a>
283 <ol>
284 <li style="display: none; ">
285 <a>h3Name</a>
286 </li>
287 </ol>
288 </li><li>
289 <a href="#H2-4">Package format and scripts</a>
283 <ol> 290 <ol>
284 <li style="display: none; "> 291 <li style="display: none; ">
285 <a>h3Name</a> 292 <a>h3Name</a>
286 </li> 293 </li>
287 </ol> 294 </ol>
288 </li> 295 </li>
289 <li style="display: none; "> 296 <li style="display: none; ">
290 <a href="#apiReference">API reference</a> 297 <a href="#apiReference">API reference</a>
291 <ol> 298 <ol>
292 <li> 299 <li>
(...skipping 115 matching lines...) Expand 10 before | Expand all | Expand 10 after
408 </ol> 415 </ol>
409 416
410 417
411 <p> 418 <p>
412 <b>Do not lose the private key!</b> 419 <b>Do not lose the private key!</b>
413 Keep the <code>.pem</code> file secret and in a safe place. 420 Keep the <code>.pem</code> file secret and in a safe place.
414 You'll need it later if you want to do any of the following: 421 You'll need it later if you want to do any of the following:
415 </p> 422 </p>
416 <ul> 423 <ul>
417 <li><a href="#update">Update</a> the extension</li> 424 <li><a href="#update">Update</a> the extension</li>
418 <li>Upload the extension using the 425 <li><a href="#upload">Upload</a> the extension to the Chrome Web Store</li>
419 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Develope r Dashboard</a></li>
420 </ul> 426 </ul>
421 427
422 <p> 428 <p>
423 If the extension is successfully packaged, you'll see a dialog like this 429 If the extension is successfully packaged, you'll see a dialog like this
424 that tells you where to find 430 that tells you where to find
425 the <code>.crx</code> and <code>.pem</code> files:</p> 431 the <code>.crx</code> and <code>.pem</code> files:</p>
426 <p></p> 432 <p></p>
427 433
428 <img src="images/package-success.gif" width="554" height="208"> 434 <img src="images/package-success.gif" width="554" height="208">
429 435
(...skipping 31 matching lines...) Expand 10 before | Expand all | Expand 10 after
461 467
462 <li> 468 <li>
463 Click <b>OK</b>. 469 Click <b>OK</b>.
464 </li> 470 </li>
465 </ol> 471 </ol>
466 472
467 <p>If the updated extension is successfully packaged, you'll see a dialog like t his:</p> 473 <p>If the updated extension is successfully packaged, you'll see a dialog like t his:</p>
468 474
469 <img src="images/update-success.gif" width="298" height="160"> 475 <img src="images/update-success.gif" width="298" height="160">
470 476
471 <a name="H2-2"></a><h2>Packaging at the command line</h2> 477
478 <h2 id="upload"> Uploading a previously packaged extension to the Chrome Web Sto re</h2>
479
480 <p>
481 You can use the Chrome Developer Dashboard
482 to upload an extension that you've previously packaged yourself.
483 However, unless you take special steps,
484 the extension's ID in the Chrome Web Store
485 will be different from its ID in the package you created.
486 This different ID might be a problem if you've
487 distributed your extension package,
488 because it allows users to install multiple versions of your extension,
489 each with its own local data.
490 </p>
491
492 <p>
493 If you want to keep the extension ID the same,
494 follow these steps:
495 </p>
496
497 <ol>
498 <li> Rename the private key that was generated
499 when you created the <code>.crx</code> file to <code>key.pem</code>. </li>
500 <li> Put <code>key.pem</code> in the top directory
501 of your extension. </li>
502 <li> Compress that directory into a ZIP file. </li>
503 <li> Upload the ZIP file using the
504 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Deve loper Dashboard</a>. </li>
505 </ol>
506
507
508 <a name="H2-3"></a><h2>Packaging at the command line</h2>
472 509
473 <p> 510 <p>
474 Another way to package extensions 511 Another way to package extensions
475 is by invoking <code>chrome.exe</code> at the command line. 512 is by invoking <code>chrome.exe</code> at the command line.
476 Use the <code>--pack-extension</code> flag 513 Use the <code>--pack-extension</code> flag
477 to specify the location of the extension's folder. 514 to specify the location of the extension's folder.
478 Use <code>--pack-extension-key</code> 515 Use <code>--pack-extension-key</code>
479 to specify the location of the extension's private key file. 516 to specify the location of the extension's private key file.
480 For example: 517 For example:
481 </p> 518 </p>
482 519
483 <pre>chrome.exe --pack-extension=c:\myext --pack-extension-key=c:\myext.pem 520 <pre>chrome.exe --pack-extension=c:\myext --pack-extension-key=c:\myext.pem
484 </pre> 521 </pre>
485 522
486 <p> 523 <p>
487 To suppress the dialog, 524 To suppress the dialog,
488 add <code>--no-message-box</code> to the command. 525 add <code>--no-message-box</code> to the command.
489 </p> 526 </p>
490 527
491 <a name="H2-3"></a><h2>Package format and scripts</h2> 528 <a name="H2-4"></a><h2>Package format and scripts</h2>
492 <p> 529 <p>
493 For more information on the format, as well as pointers to scripts you can use 530 For more information on the format, as well as pointers to scripts you can use
494 to create <code>.crx</code> files, see <a href="crx.html">CRX Package Format</a> . 531 to create <code>.crx</code> files, see <a href="crx.html">CRX Package Format</a> .
495 </p> 532 </p>
496 </div> 533 </div>
497 534
498 <!-- API PAGE --> 535 <!-- API PAGE -->
499 <div class="apiPage" style="display: none; "> 536 <div class="apiPage" style="display: none; ">
500 <a name="apiReference"></a> 537 <a name="apiReference"></a>
501 <h2>API reference: chrome.apiname </h2> 538 <h2>API reference: chrome.apiname </h2>
(...skipping 199 matching lines...) Expand 10 before | Expand all | Expand 10 after
701 _uff=0; 738 _uff=0;
702 urchinTracker(); 739 urchinTracker();
703 } 740 }
704 catch(e) {/* urchinTracker not available. */} 741 catch(e) {/* urchinTracker not available. */}
705 </script> 742 </script>
706 <!-- end analytics --> 743 <!-- end analytics -->
707 </div> 744 </div>
708 </div> <!-- /gc-footer --> 745 </div> <!-- /gc-footer -->
709 </div> <!-- /gc-container --> 746 </div> <!-- /gc-container -->
710 </body></html> 747 </body></html>
OLDNEW
« no previous file with comments | « no previous file | chrome/common/extensions/docs/static/packaging.html » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698