I have a colleague who built a database app using ReTool.
Since it has been built quite nice, we would like to publish it on our cloud space and make it accessible for more than just him.
But we can't find any information on how to publish the app, apart from the in-app settings, to publish it, but it is always a "preview" version.
Anyone has experience with this?
You can share your Retool app publicly via a public link, and embed it in an iFrame in other applications or web pages. In edit mode just click the "Share" button on the top right and select the "Public" tab. (This will render your app publicly.)
But It's good to know that the public apps are only available on the Business and Enterprise plans.
Check this link for detailed information.
You can also get the share app url from (...) menu.
Related
When I test my app using a web preview, it shows the above page.
I do not know how to install it? Set? Storage Access API
Where to install Storage Access API?
Before you can use the Cloud Shell these are steps you should follow:
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
Note:
If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.
Go to project selector
Make sure that billing is enabled for your Cloud project. Learn how to check if billing is enabled on a project.
Then follow the following steps below to enable the API in your own Google Cloud project.
In the Cloud console, go to APIs & services for your project.
Go to APIs & Services
On the Library page, click Private APIs. If you don't see the API listed, that means you haven't been granted access to enable the API.
Click the API(look for Storage Access API) you want to enable. If you need help finding the API, use the search field.
On the page that displays information about the API, click Enable.
Reference:
https://cloud.google.com/shell/docs/run-gcloud-commands
https://cloud.google.com/endpoints/docs/openapi/enable-api#console
It might be already enabled but there is a bug in this page so you need to re-authenticate
Open developer tools in your browser and select Network
you will find a line starting with accounts.google.com open it and authorize cloudshell.
I want build site using Sitecore(7.2) and also make it offline. Our requirement is not to use headless CMS. Is there any way to build or make it offline?
Internet websites cannot be delivered 'offline' without having all possible data delivered to the device so that it no longer needs to connect to the internet. This sounds less like a website, and more like an app that somebody would install?
If so, you probably DO need to look at headless and building an app that connects to the APIs for updates.
You might need to be more specific about the business use case because it seems contradictory to want to use a web application software that delivers web content, without using headless, and works without the web.
As already suggested that internet websites cannot work offline so either you have an app or intranet website.
Considering as an app you can consume sitecore OData apis for Content/Media however it will not work for Presentations and you have to implement your own mobile designs based on Xamarin or native.
For odata related information you can refer below link:
https://doc.sitecore.com/developers/90/sitecore-experience-manager/en/the-odata-item-service.html
Once you get the response from api, you can locally store it in your local db of app
Essentially, I'm wanting to create an Oauth Client as an App so I can get data from Dynamics for multiple customers. Does anyone know if this is possible to do in AppSource or do you know of another way?
I have a service that will be served in a cloud different than Azure so there really isn't anything for me to submit as an App and I really don't want every customer to have to setup their own App that gives my service the privileges/access it needs, but it's looking like I may have to.
It sounds like you'll want to register an app with Azure AD (the OAuth2.0 service/identity provider for work and school accounts), and create a multi-tenant app. Then you can configure this app in the Azure Portal to get permissions to the APIs the app wants tokens to call (in your case Dynamics or the Microsoft Graph).
Once this app is written, you can code up your app using one of the Azure AD Auth Libraries. Here's some sample code for a .NET web API. You can find more code samples on Github and search active directory. Moreover, the Azure Active Directory Developer Landing Page is a great place to look for more resources on doing all of this.
As a collection administrator I am not able to access site settings on SharePoint site collection. if I click on site settings it showing "sorry, this site has doesn't share with you". But I login using site collection administrator account on dev server.
If I create new site collection with same web application I can access everything. one more thing I restored production database on this server and I associated with this web application.
I hope anyone can help to this issue please.
This might happen as the production environment will have different users and when you restore it to your development environment, your development environment changes were override.
To fix this issue, go to Central Administration -> Application management. Under site collection section, click on "Change site collection administrators".
In this select your site collection. Change site collection administrator and click ok.
So here is the scenario:
I have a MOSS 2007 box and I want my clients to be able to access a SharePoint site via the internet. I am told that I will be using an IPA and AD for authentication. However I have a DB outside of SharePoint that holds various business data and I want to use Web Services to access the data, manipulate it, and send it back to SharePoint via web parts.
The issue is that, from what I understand, I am going to have to authenticate the AD user every time a request to the Web Service happens. Obviously I dont want to do this every time because they have already authenticated to get onto the site, however I do want each call to have some form of security so its not open calls to my db. I do plan on having other applications access this service outside of SharePoint, so I dont want to have to reinstall the service for each application or even again.
Has anyone had to perform this task or something similar or do you have any suggestions on how to do this?
Thank you in advance and happy coding!
Why not just deploy the webservice to Sharepoint using a Sharepoint solution and a Feature.
That way it will be running under the sharepoint app pool and all authentication is done by sp.
Edit:
Seeing that SharePoint should not be in "control" (as stated in the comment), you should create the webservice, and run the application it's under in as using Windows Authentication. IMHO you should create a WCF Service. The, using the information found in this article you make the Service authenticate users against the AD usergroups they are in. see the "Security: Authentication" section of the article.
Then in Visual Studio you create a webpart and add a service reference to the project, pointing to your newly created Service. Have the webpart perform the needed logic (i.e. display data etc.)
Deploy the webpart to SharePoint using a SharePoint solution (.wsp files, created with WSPBuilder). Google for SharePoint + wspbuilder + tutorials. The solution should contain 1 feature to deploy the webpart. WSPBuilder integrates with VS and allows for the creation of WSPBuilde project. add a webpart feature item to the project (it will create the xml (deployment related) and code file for the webpart.