Box api-content developer account to production ready account - box-api

I currently have a developer account setup in box and looking for steps to move it to production. I cannot find details on
If there is number of users allowed
How to turn production mode on
I am have setup initial account with auth redirect url. Configured my app key and token in my web application.

In terms of "productizing" I've heard a few different ways this term
1) To just make an app generally useable among consumers of the third party app, all that is needed is a functional integration with Box APIs. Assuming that you have implemented oAuth correctly and integrated our APIs functionally, there is no barrier to everyday users to using that integration between Box + third party app.
2) To make an app available to Box users ("productionalize" is a term I hear often), the best way to do this is through our gallery. Developers can follow these instructions for creating a listing in our App Gallery: cloud.box.com/appgallerylisting

Related

Guidance on app submitted to AppSource that targets Enterprise B2B Customers

We recently submitted our Add-in for approval to be available on AppSource/Office Store and failed approval. Some of the feedback and policies make sense and we have addressed those items. However, there are a few policies that I'm not sure how to address and looking for guidance.
Policy 7.1 & 7.16 are about the supportURL not being publicly available and requiring Sign-in. Our add-in is not a general user add-in but targeted to Enterprise Customers of our Platform. They are provided a login for our support site so is this not sufficient? Do we really need a public url for an add-in targeted to Enterprise Customers?
As I was writing this I found the following link and wanted to make sure this was still valid and the same guidance for my scenario: App Submission - Help/Support Link Requirement
Policy 11.3 are about the Start-up experience needs to engage the user and show value proposition. Our users are Enterprise Users and have signed up for platform in which we will already guide them to use the Excel Add-in. Since they already know the value proposition from our sales team is there a way that this can be handled in our scenario without needing an explicit startup video or wizard walk through of app features?
Yes, this must be a public URL. The support link in your Seller Dashboard listing appears on the AppSource website so must be publicly available. It can be a link to your main website / or a contact page on your main website.
Have you seen the documentation on submitting Enterprise add-ins? This outlines which policies are not applicable when submitting an add-in which targets larger organizations and enterprises. It also explains how to declare, via test notes, that you are submitting an Enterprise add-in.

Considering Tyk API Gateway - open source version

Project background: Building an API driven Learning Management System. The back-end system will be receiving data from multiple systems and interfaces: web, mobile, VR.
Looking at API Gateways to front our APIs. Preferably an Open Source API gateway but need to be sure that the support and service is available. Tried out Tyk.io and it feels like it might be the way to go. Been reading other StackOverflow threads around this and looks like TYK's gateway fairs quite well against the likes of Kong and WSO2.
Main areas of consideration for us are:
Rate-limiting
Open ID Connect authentication
Analytics
Scalability
Hybrid model of hosting - combination of on-prem and cloud depending on compliance requirements of educational institutes (Probably rules of AWS' gateway)
It would be really helpful if anyone who is using or has used TYK.io for their production projects can share their experience, especially for enterprise clients/projects.
Full disclosure: I work for Tyk, so of course think that Tyk is the best fit for your project ;)
Seriously, though - Tyk can do all those things you’re after. Here are some links to the documentation for each item that is big on your list:
Rate-limiting
Open ID Connect authentication
Analytics
Scalability
Hybrid model of hosting
You can also post on the Tyk community for help, if you haven’t already, or search to see what else others have said.
The Tyk Open Source API Gateway will do everything you need, even outputting analytics to difference sources, like ElasticSearch, Mongo or just CSV.
In addition, you can also use our API Management Platform to control your open source gateway. The Tyk API Management platform includes a Dashboard with analytics and out-of-the-box developer portal. Tyk is free to use, under a developer license, to manage a single gateway node, ideal if you are doing a POC.
Hope this helps and please keep in touch to let us know more about your use case.

Apps monitoring on Openshift

Once I have deployed my application on Openshift, what is the recommended way / best practice of collecting the: 1) CPU, 2) network, 3) memory, 4) disk storage usage of the app? Basically to monitoring an app.
The best would be if they could be displayed in a time series format. Is it possible to link it with 3rd party service (e.g. New Relic) to do that?
Thanks.
I would say that new relic would be the best way to go for most folks. OpenShift does have a marketplace that brings in lots of different 3rd-party solutions like and makes them super easy to integrate. New Relic is available and best of all you can do it for free. You can go to marketplace.openshift.com to add new relic and there's even a KB that will walk you through it step by step here: https://help.openshift.com/hc/en-us/articles/203467070-How-do-I-add-New-Relic-to-my-application-in-the-OpenShift-Marketplace-.
For the sake of stackoverflow, here are the contents of that article:
1. Go to marketplace.openshift.com and login in
2. Locate New Relic
3. Click on "Try the Free Edition"
4. Complete checkout steps.
This will create your www.newrelic.com account. You can confirm this by going to
purchased products at the top of the page. Then to your new relic add-on and click on "New Relic". This should bring you over to newrelic.com and automatically log you in with your OpenShift marketplace account.
To add New Relic to an individual OpenShift application.
Click on Purchased Products
In the New Relic Section, you should have something like "newrelic_6a260 Standard" and a "add to apps" button.
Click on the "add to apps" button
Select the application you want to add New Relic to.
There are two other options you can use.
AppDynamics - I have used their tools and I really like it for monitoring. It is available as well through the Online Store
DataDog - I have not used them but I have seen the demos at their booth and it looks really good as well.
Would love to hear what you choose and your experience.
You should consider Sysdig Container Monitoring
Of all the tools mentioned, it's the only one that was purpose-built for containers. It uses the metadata from openshift to allow you to group containers dynamically into services (namespaces, deployments, etc).
It gives you host, container, and application metrics, including response time of containers and services using network data.
It provides custom alerting and dashboarding as well.
Finally, if you're the service provider, they have a functionality that enables "service-based access controls" - basically allowing you to limit data access to certain services, again, based on the Openshift's metadata.
Sysdig can be used as a cloud service or as on-premise software depending on your use case. Here is a link to their open shift commons briefing: https://www.youtube.com/watch?v=-w-OD78Hno0

How do I deploy my box.net application

I have create an box.net application according to the documentation.
Now, I would like to share the application with my colleges. Does anyone knows, how I can make it? IMPORTANT, I dont want to deploy it in public.
Thanks in advance
It really depends on what kind of Application you've created. There are fundamentally 2 types of apps in the Box "App Marketplace"
1) Apps that run on a server at a URL you own. Box sends calls to you, either for file-actions (think right-click, open-with kinda stuff), or for webhooks.
2) Apps that are built for a specific device (like an iPhone or Android). They show up in our marketplace, but the download links take users to the itunes or an android store to download the app. These apps call into Box via APIs (see https://developers.box.com/docs)
If you've built a #1, then you need to figure out where you want to host the software you wrote. Box makes it easy to host it on Heroku, or CloudFoundry, or Parse, so you can get going quickly, without having to provision your own hardware, etc.
So, it really depends on what kind of application you've built.

Reason for installation through Chrome Web Store

Is there a technical reason, why a Google Drive application must be installed through the Chrome Web Store (which severely limits the number of potential users)?
The reason that installation is required is to give users the ability to access applications from within the Google Drive user interface. Without installation, users would have no starting point for most applications, as they would not be able to start at a specific file, and then choose an application.
That said, I realize it can be difficult to work with in early development. We (the Google Drive team) are evaluating if we should remove this requirement or not. I suspect we'll have a final answer/solution in the next few weeks.
Update: We have removed the installation requirement. Chrome Web Store installation is no longer required for an app to work with a user's Drive transparently, but it is still required to take advantage of Google Drive UI integrations.
To provide the create->xxx behaviour that makes a new application document from the drive interface, and to be able to open existing documents from links, there must be some kind of manifest registered with Google's systems and some kind of agreement from the user that an application can access your documents and work with specific file types. There's little way around this when you think about the effects of not doing this.
That said, there are two high level issues that make for compatibility problems.
As the poster says, the requirement to install in the chrome store
severely limits the number of potential users.
But why? Why do the majority of Chrome Web Store applications say that they only work on Chrome? Most of these are wrappers to web applications that work on a range of browsers, yet you click through a selection and most display "works on chrome", aka only installs on chrome.
Before we launched our application on chrome we found that someone had created "xxxxxxx launcher" in the store, that simply forwards to our web app page. We're still wondering why it only "works on chrome". I suspect that some default template for the web store has:
"container" : "CHROME",
in it, which is the configuration option to say chrome only. That said, I can't find one, so I'm very confused why this is. It would be healthier if people picked Chrome because it's the better browser (which it is in a number of regards), not because their choice is limited if they don't. People can always write to the application vendor and ask if this limitation is really necessary.
The second thought is that a standardised manifest format across cloud storage providers would mean a much higher take up in web app vendors. Although, it isn't hugely complex to integrate, for example, with Google Drive, the back-end and ironing out the the details took over a week in total. Multiply that lots of storage providers and you have you lose an engineer for 2 months + the maintenance afterwards. The more than is common across vendor integration, the more likely it is to happen.
And while I'm on it, a JavaScript widget for opening and saving (I know Google have opening) by each cloud storage provider would improve integration by web app vendors. We should be using one storage providers across multiple applications, not one web application across multiple storage providers, the file UI should be common to the storage provider.
In order to sync with the local file system, one would need to install a browser plug-in in order to bridge the Web with the local computer. By default, Web applications don't have file I/O permissions on the user's hard drive for security reasons. Browser extensions, on the other hand, do not suffer from this limitation as it's assumed that when you, the user, give an application permission to be installed on your computer, you give it permissions to access more resources on the local computer.
Considering the add-on architectures for different browsers are different, Google first decided to build this application for their platform first. You can also find Google Drive in the Android/Play marketplace, one of Google's other app marketplaces.
In the future, if Google Drive is successful, there may very well be add-ons created for Firefox and Internet Explorer, but this of course has yet to be done and depends on whether or not Google either releases the API's to the public or internally makes a decision to develop add-ons for other browsers as well.