My company has an application related to workflow automation and we need to deploy it on Google Market place for work. But before making it live or (other customers can view/download it) we need to test our application on a market place. I need to ask if there is a way to test application before deployment or any sandbox testing environment available?
Any help is highly appreciated.
Kind regards
When publishing your app in the Chrome Developer Dashboard you can publish to your test accounts. Your app will be visible only for those accounts. Here you can find more info on that.
Related
I'm trying to get review apps up and running on Heroku. In my usecase I have a bunch of custom domains and I have postdeploy and pr-predestroy scripts that correctly setup all of that. However ACM is not getting enabled for the new apps, so none of the URL's gets certs until someone goes and manually enables ACM. Is there a way to have ACM automatically enabled for new review apps? If it matters any we are manually triggering the creation of the review apps.
The best answer I found was to use the platform API to enable ACM from the postdeploy script https://devcenter.heroku.com/articles/platform-api-reference#app-enable-acm
I am developing an app that uses Directory API to create user accounts within Google Apps for Work. I have been testing this on a Free (legacy) account but now I need to test adding and removing domains, which Free account doesn't support. I don't want to get a paid account just yet and rack up a huge bill by adding and removing accounts in testing. I also don't see a way to get a sandbox/developer account to test this out. How can I accomplish this?
Is there any easy way to repeatedly test the installation process of a Google Marketplace App on a new domain? It seems as though when you try to install an app to a domain to which it's already been installed, parts of the process are short-circuited, even if the app's permissions on that domain have been revoked. Is there any way around this short of registering a throwaway domain for every test? Being able to automate this test would be even better, but even a repeatable manual test would be very useful.
Unfortunately you need to delete the application and install it again each time from what I gather.
You can revoke the auth here: https://www.google.com/a/your-domain-here/IssuedAuthSubTokens
You definitely don't need to register throwaway domains every time.
If you're trying to test your integration, there is "TEST INSTALL FLOW' button right in the Google APIs Console that starts a test flow. Here's a screenshot:
That's especially useful when you want to test your integration before it is published to the Google Apps Marketplace (but it still works once it is published.)
If you actually install it from the Marketplace as a tester or once published, you can go to the app listing and remove the app. Since we've launched I've added and removed my apps that way quite a few times :) Here's a screenshot:
#aleckz suggestion won't actually work since tokens are Admin authorized and not revokable by the domain user.
Jelastic docs http://docs.jelastic.com/app-packaging says that it is possible to pack application to make it much easier to install for the end-user.
But no information how to pack application and create such button.
Any thoughts about that?
It mostly relates to Hosting Providers, they can pack any available app and then get it published for end-users. But you as end-user can easily contact your Hosting Provider support services and discuss application you want to be available via "One CLick Button intsallation".
Why should I use AppHarbor addons when I can get an account directly from the provider and have additional benefits (like multiple users or projects per account)? I know having addons per application centralizes configuration but it also means you have to go through AppHarbor.
In addition AppHarbor adds their header on the website of some providers (notably Airbrake), which ruins the design (looks out of place and has massive margins). On some addons pricing is much more flexible than the addon pricing (again, Airbrake is a good example - no idea what those plans offer!).
Provisioning add-ons through AppHarbor gives you the advantages of automatic application configuration, consolidated billing and being able to manage everything from AppHarbor (and not having to remember X logins and not having to remember to keep X credit cards updated at various services providers).
We've tried to make make the header as inconspicuous as possible, and it seems to work well on most of our add-on partners sites. Please drop us a line at if it causes breakage anywhere.
We're also continuously working with our add-on partners to keep their add-on plan offerings up-to-date and I've just shot the AirBrake guys an email. Thanks for alerting us to the problem!