“It wouldn’t be hard for a competent hacker to add real database support. “AppDrop is open-source just like the Google SDK, so I’m hoping someone will come along and take it to the next level,” he said. I spoke to Chris this morning about his project and where he wants it to go. This means issues with performance and no scalabity to speak of, but for apps with limited resource needs, something as simple as AppDrop would work fine. The App Engine SDK doesn’t use BigTable for its datastore, instead relying on a simple flat file on a single server. Of course, this simple portability comes at the cost of scalability. For example, here’s Anderson’s Fug This application running on Google App Engine and the identical code running on EC2 at AppDrop. As a result, any application that works with the App Engine SDK should work flawlessly on AppDrop. How does it work? Behind the scenes, AppDrop is simply a remote installation of the App Engine SDK, with the user authentication and identification modified to use a local silo instead of Google Accounts. This proof-of-concept was built in only four days and can be deployed in virtually any Linux/Unix hosting environment, showing that moving applications off Google’s servers isn’t as hard as everyone thought. Just like Google’s Appspot, anyone can use a modified SDK to deploy their App Engine apps directly to Amazon EC2 instead of Google, and they work without modification. This morning, Chris Anderson, the Portland-based cofounder of the MP3 blog service, just released AppDrop - an elegant hack proving that’s not true.ĪppDrop is a container for applications developed with the Google App Engine SDK, running entirely on Amazon’s EC2 infrastructure. Module_configuration = ModuleConfiguration(config_path, app_id)įile “E:Program filesGoogle app enginegoogleappenginetoolsdevappserver2application_configuration.py”, line 113, in _init_įile “E:Program filesGoogle app enginegoogleappenginetoolsdevappserver2application_configuration.One of the biggest criticisms of Google’s App Engine have been cries of lock-in, that the applications developed for the platform won’t be portable to any other service. “Browse” button is not able to help you, type manually.įile “E:Program filesGoogle app enginedev_appserver.py”, line 82, inįile “E:Program filesGoogle app enginedev_appserver.py”, line 78, in _run_fileĮxecfile(_PATHS.script_file(script_name), globals_)įile “E:Program filesGoogle app enginegoogleappenginetoolsdevappserver2devappserver2.py”, line 986, inįile “E:Program filesGoogle app enginegoogleappenginetoolsdevappserver2devappserver2.py”, line 979, in mainįile “E:Program filesGoogle app enginegoogleappenginetoolsdevappserver2devappserver2.py”, line 722, in startįile “E:Program filesGoogle app enginegoogleappenginetoolsdevappserver2application_configuration.py”, line 740, in _init_ To run it locally, right click on the helloworld.py, choose “Run As” –> “Run Configuration”, create a new “ PyDev Google App Run“.įigure 5.1 – In Main tab -> Main module, manually type the directory path of “ dev_appserver.py“. ![]() ('Hello, webapp World!')Īpplication = webapp.WSGIApplication(, debug=True)įile : app.yaml – GAE need this file to run and deploy your Python project, it’s quite self-explanatory, for detail syntax and configuration, visit yaml and app.yaml reference. File : helloworld.py – Just output a hello world.įrom .util import run_wsgi_app
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |