You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mike Meyer edited this page Jul 28, 2013
·
1 revision
Step 1 (it’s a biggie).
Copy your Chrome private key to a directory that’s accessible from the command
line. I keep mine in ~/Repositories/certificates/. Make sure the private key
(.pem file) is named chrome.pem.
You’ll need to do some shenanigans to get your Safari certificates exported.
The details are in this blog post but I’ll summarize it here when I
have more time.
Put the results of that blog post in your certificates directory. Make sure
the Safari private key is named safari.pem.
You should have the following files in your certificates directory:
chrome.pem
safari.pem
cert00
cert01
cert02
Step 2
Add browser-extension-build-utils as a submodule to your git repository. You
can specify the directory the submodule will be cloned into if you want
something a little less cumbersome than browser-extension-build-utils.
I use utils.