Google App Engine provides an experimental, bleeding-edge OAuth service in its Python SDK, but fails to provide simple example to work with. Has anyone succeeded in working with it? If so, could you provide a snippet?
Here is a very good tutorial
Related
I'm trying to setup a flask app on google app engine that will be something of a frontend management console for google container engine. Google has put out working APIs to spin up a container cluster, but it does not look like they have put out (python) APIs to administer kubernetes. That is, everything needed implement services, pods, RCs etc. seems to be setup to run through bash scripting. This is not compatible with the restrictions of google's app engine.
Is there a commonly accepted solution/package for this? Would it make more sense to abandon appengine in favor for a managed VM (not ideal)?
Thanks
As I mentioned in Submit jobs using API Client Library for Python?, the Kubernetes API uses a standard swagger specification, so it should be possible to generate a python client library. There is also pykube if you want to experiment with a existing client library.
I'm developing a Google App Engine application and I am encountering references to both an App Engine SDK and a Cloud SDK.
How do these two SDKs relate to each other?
There is definitely some overlap between the two. There is a dev_appserver.py and appcfg.py is both of them. I can run a development server using dev_appserver.py, and also with gcloud preview app run.
Why are there two tools that do the same thing? Is one being deprecated in favor of the other? Is there a roadmap for merging the toolsets, or are they going to be maintained in parallel? Do I need both, or just one?
It seems like the Cloud SDK is the more general of the two. But is it a superset? I.e. can I do anything I can in the App Engine SDK with the Cloud SDK?
I'm very confused by this messy and undocumented setup.
The App Engine SDK is older and was designed specifically for App Engine.
The Cloud SDK is newer and its goal is to cover other (all?) Google Cloud products, not only App Engine. So they definitely overlap in functionality from the App Engine's perspective. Specifically from this perspective the Cloud SDK appears not yet as mature and stable as the App Engine SDK. For example the gcloud preview portion is still at a BETA version:
NAME
gcloud preview app - (BETA) manage your App Engine app
As long as your work would be contained in the App Engine environment you can pick either of them, as you prefer.
If you throw in the mix third party tools or IDEs integration support the balance tips towards the App Engine SDK for now (PyCharm, for example).
I guess Google will eventually deprecate the App Engine SDK in favour of the Could SDK, but so far I didn't hear any such announcement. A similar deprecation trend already started in the (old) GAE Console - stuff being gradually migrated to the Developer Console.
Documentation says
The preferred tooling for managing your App Engine applications in PHP is now the Google Cloud SDK. The Google Cloud SDK includes a local development server as well as the tooling for deploying and managing your applications in App Engine. Optionally, you can also download the original App Engine SDK for PHP.Optionally, you can also download the original App Engine SDK for PHP.
Though this is for PHP, I believe similar upgradation for other languages too.
I'm looking for a while now for a good code example about how tu use the google-api-python-client in Django on Google App Engine.
I found out in another question that the very cool decorator isn't fit for Django.
There is a code example for the google-api-python-client but neither does it make use of Google App Engine nor is it at all documented.
I can't be the only person, that wants to use django on GAE and implement the API. I would be very grateful for some wisdom.
I'm struggling to get Windows Live Web Authentication running on Google App Engine (GAE) using Python, as I'm quite new to the language.
However there are lots of examples for Facebook and Twitter, I was wondering if anyone had come up with a solution for Windows Live yet?
From what I can tell, the SDK you're referring to is just used for authentication, not authorization. That is, it allows you to uniquely identify a user by their Windows Live ID, but not, say, programmatically import their Hotmail contacts.
If this is the case, it would be easier to use the built-in OpenID support that's already available on both sides. The Windows Live OpenID provider is OpenID.Live-INT.com; instructions for authenticating using OpenID on App Engine can be found # http://code.google.com/appengine/articles/openid.html.
I ended up using http://anyopenid.com which provides quite a good bridge to openid, and I was able to use this with Google App Engine.
I'm wondering if anybody tried to integrate mosso CloudFiles with an application running on Google AppEngine (mosso does not provide testing sandbox so I cann't check for myself without registering)? Looking at the code it seems that this will not work due to httplib and urllib limitations in AppEngine environment, but maybe somebody has patched cloudfiles?
It appears to implement a simple RESTful API, so there's no reason you couldn't use it from App Engine. Previously, you'd have had to write your own library to do so, using App Engine's urlfetch API, but with the release of SDK 1.1.9, you can now use urllib and httplib instead.