Closed thom4parisot closed 8 years ago
Would be great! I'm doing this manually with a compress task.
The same :-)
question: since it's a zip file, how can Chrome Store tell if it's the same extension? while the crx file need a private key to pack?
It knows that because you upload it on the Webstore admin page. It generates a crx and distributes it for you.
I see. Is there an easy way to auto migrate users from the chrome extension from the Chrome store to a self-hosted version?
Well I think you can grab the signing key from the Webstore admin UI, not sure about it though.
Otherwise you can restrict the extension to a specific Google Apps domain.
Google announced they will remove manual installs of extensions on Windows soon so you should take that into account in your shift.
Does the chrome web store have an API that would allow us to automate publishing new revs?
Answer my own question: https://developer.chrome.com/webstore/using_webstore_api
Man I hate OAuth for APIs like this that are meant for automation... I wish they would just let you use SSH keys.
@joshperry oh this is new! I did not know about that. A good way with oauth is to store the OAuth with root access only (if the user has root access…).
I found this project and forked it, don't dig the underscore naming style, not very idiomatic Grunt, and I would like a flow that doesn't involve popping a browser: https://github.com/joshperry/grunt-webstore-upload
Looks like the functionality of these two code-bases may be good candidates for merging.
@joshperry well I would suggest you to make it a non-grunt specific package so as grunt-crx
could use it as a dependency :-) Is it something you would be confident to do?
It would be simple enough to make the packaging and uploading for the web store separate grunt tasks that could be used by grunt-crx
.
@joshperry excellent! Keep me posted :-)
And thus, package as ZIP instead of CRX.