I have a script that I would like to make available to all the users of our Google Apps domain, but I don't want to publish it to the Chrome store. We would like to avoid deploying it from a single user account. How is this normally done?
1 Answer
It really depends on your use case, but there are a number of ways this might be achieved from publishing a code library (and limiting the sharing of the link), hosting it in a Google Site to publishing it as a url triggered webservice.
It depends on whether you want to share the functionality to others or literally the code.
1 Comment
Greg
Both, now that you mention it. Thanks for the input - I really like the idea of deploying a url triggered web app, and linking to it via an extension or an installable app in Chrome. The crx files could be deployed with the browser and distributed that way.