#python#alibabacloud#android#android_emulator#aws#azure#cloud#docker#docker_android#emulator#gcp#genymotion#jenkins#kubernetes#mobile_app#mobile_web#novnc#saltstack#selenium#selenium_grid#terraform
You can use Docker-Android to run Android emulators inside Docker containers, which helps you develop and test Android apps easily without needing physical devices. It offers many device profiles like Samsung Galaxy and Nexus models, supports viewing the emulator via VNC, sharing logs through a web interface, and controlling the emulator remotely with adb. It works on Ubuntu and can integrate with cloud services like Genymotion. This setup speeds up development, testing, and automation, making your workflow more consistent and efficient while saving resources. You can also persist data and run unit or UI tests with popular frameworks like Appium and Espresso. This helps you build and test Android apps faster and more reliably.
https://github.com/budtmo/docker-android
https://pypi.python.org/pypi/oauthlib
A generic, spec-compliant, thorough implementation of the #OAuth request-signing logic for python
OAuth often seems complicated and difficult-to-implement. There are several prominent libraries for handling OAuth requests, but they all suffer from one or both of the following:
They predate the OAuth 1.0 spec, AKA RFC 5849.
They predate the OAuth 2.0 spec, AKA RFC 6749.
They assume the usage of a specific HTTP request library.
OAuthLib is a generic utility which implements the logic of OAuth without assuming a specific HTTP request object or web framework. Use it to graft OAuth client support onto your favorite HTTP library, or provide support onto your favourite web framework. If you’re a maintainer of such a library, write a thin veneer on top of OAuthLib and get OAuth support for very little effort.
https://aaronparecki.com/2012/07/29/2/oauth2-simplified#others
OAuth 2 Simplified
Sun, Jul 29, 2012 9:30am -07:00
Many services such as #Facebook, #Github, and #Google have already deployed OAuth 2 servers, and deployed implementations win.
The #OAuth 2 spec itself leaves many decisions up to the implementor. Instead of describing all possible decisions that need to be made to successfully implement OAuth 2, this post makes decisions that are appropriate for most implementations.
This post is an attempt to describe OAuth 2 in a simplified format to help developers and service providers implement the protocol.