Direction on Google design pattern [closed] - python

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I need to build a app which has the following design pattern.
Results displayed on iOS device.
User data stored online (more than
just username/password, also data they themselves put in).
User can sign in with TW/FB etc.
Computation logic code running on backend, which will need to gather data from online sources, and produce results. The server code will be Node.js or Python.
I think some combination of Firebase and Google App engine will work, but I'm not exactly sure which of the design patterns in the following link is the one I'm looking for.
https://cloud.google.com/solutions/mobile/mobile-app-backend-services#design-pattern
?

Based on your description, I think the second one will work best.
https://cloud.google.com/solutions/mobile/mobile-app-backend-services#firebase-appengine-standard
You will likely need to use firebase queue to do what you're planning to do.
https://firebase.googleblog.com/2015/05/introducing-firebase-queue_97.html
Results displayed on iOS device.
Using iOS firebase calls
User data stored online (more than
just username/password, also data they themselves put in).
Using iOS fireabse calls
User can
sign in with TW/FB etc.
Using firebase authentication
Computation logic code running on backend,
which will need to gather data from online sources, and produce
results. The server code will be Node.js or Python.
Using firebase queue running on google app engine

Related

How can I restrict API token access for users while giving them API access using Python? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 days ago.
Improve this question
I currently have a Flask application that allows users to submit a set of form data which is then used to query an API. This API requires an API token for authentication. I want users of my Flask application to be able to make queries to this API but I don't want them to have access to the API token required to make those queries.
At a higher level, what design can I implement to allow for this. My current thinking was to host the Flask application on a dedicated server and allow only specific users (defined using a subnet CIDR block) to interact with it. The API token itself would be contained on the server and not on the local machines of the users. I would love to hear suggestions for different ways to approach this task. I am new to this area and haven't found anything online that is simple enough or relevant for my use case.
My first attempt at this involved a hacky workaround whereby the user form data submitted by users through the Flask app would be stored in a YAML file then subsequently pushed to a remote git repository. This git repository is polled periodically for changes by a Jenkins pipeline on a separate machine which takes any new changes detected and creates an API request using the configuration defined in the YAML file. I'm aware this can't possibly be the optimal solution.

How to use request(python) to use Microsoft Graph API [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I tried to use the Microsoft Graph API from the Request module in Python, but I was still new and didn't want to use Postman either. But I had a problem using the Request module:
How to select the application platform type?
How to fill in the redirect URL?
How to get refresher token and access token ?And how to renew(refresh) them?
How to get Tenant ID?
This is all my questions. I hope someone can help me solve them.
(This question by the machine translation, if there is a small mistake, also hope you understand.)
Congrats on your first question!
This is not a full answer that you might have been looking for, but take a look at the Microsoft Graph API docs
After you register your app and get authentication tokens for a user or service, you can make requests to the Microsoft Graph API.
Did you register your app? If not here are the docs
In your question it looks like you're describing the flow for get access on behalf of the user, but what you need is get access without a user. In order to use the API through the requests module you need to follow this tutorial

Get and transfer data using an API [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I have to develop an API to manage data between my Database in PostGreSQL and my website in Django.
I'm actually looking for the best way to manage and transfer this data, what I actually found on different topics / sites is the Django Rest Framework to develop a Rest API in Django, here I would use a JavaScript framework for the front like React, Angular or VueJS (any tips about which one to choose ? ).
I was wondering if there was other solutions that would be interesting ? I've been searching about FTP or things like this.
Thanks,
Lucas
Like you said you need to send and retrieve information like name, contact, login detail etc related to user and their subscriptions.
In this case you don't have to think about FTP. It isn't related here. FTP is something that you'll use to transfer files without django.
With django you will have to use DRF (django rest framework) or use GraphQL along.
There is a package well known to use GraphQl called graphene
For front end part you can use anything according to your requirement and skillset.
Hope this helps.
Cheers

Running Python on Server and sending results to Client and vice versa [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
So basically, what I want to do is have a user input some data in an HTML form or something (on client end). Have that data be carried over to a server, where the data is put through some python code and the processed result is sent back to the client. I know, I could use javascript to do this on the user side itself, but I want to experiment a bit and make use of some libraries like tensorflow, matplotlib and so on.
Also, is there some way, you know like Web Assembly to run python code on the client side. Like maybe, send data from server or have it fed by the user, and on some virtual environment type setup and processed ??
Note: I know flask exists and I've tried it, but I can't see the same flexibility as you know regular python code.
Thanks in advance 😊
There won't come a definite answer to your question because your question is too broad. But maybe this will give you some starting points.
I see you have two questions:
How can I use python server side
How can I use python client side
Question 1:
First of all you might know that it makes sense to perform operations on a server and not on a client. For example interacting with a central database.
Flask is already lightweight compared to Django which also uses python. If you really want to do a lot on your own you could take a look at websocket or common gateway interface (cgi).
Question 2: This is really not recommended but if you want to play around with WebAssembly and Python a good starting point is PyPyJs: https://github.com/pypyjs/pypyjs!
You can use Brython in the browser, it's pretty spiffy. Full dom-manipulation from python; fully compatible with libraries written in pure python. Really neat stuff.
As for the server-side, if you want to keep it full-python, you'll need to use something like flask, bottle, cherrypy, aiohttp,...
If you find yourself struggling; maybe try starting out writing a simple socket-based microservice? You'll then be able to either farm requests out to it from any other server; or incorporate the code in your (python) server code.
Good luck!

Easiest way to manage/monitor a flask app? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a small flask app I want to deploy on my server and I'd like to be able to monitor it via an HTTP web interface. I don't need something complicated and I definitely don't want something that's difficult to set up. Previously I've used the Google App engine and the functionality in the Logs tab is completely fine.
The app is served through nginx & gunicorn and uses redis (w/ py-redis) and sqlite (w/ peewee). Ideally I'd like to be able to check the logs for all parts of the system from one place. Is this possible? What's the easiest way?
There is no definitive answer to the predicament and it would be whatever way you are most comfortable with.
You could change all your logging to write to a central database then create a small program which would scrape this data for you. This method also includes configuring a central syslog server:
http://www.linuxjournal.com/content/creating-centralized-syslog-server
What ever way you want to read these files is fine and all depends how much control you want. You could simply name all the logs based on hostname and rsync them to a central server from where you could parse them.
There are also free tools out there which will aid you in choosing you method take a look at:
http://www.linuxjournal.com/content/creating-centralized-syslog-server
There are also some proprietary systems you could use, such as Splunk:
http://www.splunk.com/
This is by no means a definitive list but should aim you in the right direction.

Categories