You'll need to replace the storage engine. The flat file stand-in
google supplies is garbage, performance wise, and really doesn't
represent bigtable well at all.
Maybe check out integrating ZODB as the storage layer for the bigtable
stand-in.
On Apr 15, 4:27 am, jchris <jch...@gmail.com> wrote:
> I support the full API (excepting email sending, which could come
> along soon) and the whole project is open source, so you can fork it
> all you'd like.
> Please upload some apps, and let me know what your experience is!
> You'll need to replace the storage engine. The flat file stand-in
> google supplies is garbage, performance wise, and really doesn't
> represent bigtable well at all.
> Maybe check out integrating ZODB as the storage layer for the bigtable
> stand-in.
> On Apr 15, 4:27 am, jchris <jch...@gmail.com> wrote:
> > Hello all,
> > I just released App Drop, which is a swappable alternative to Google's
> > App Spot hosting.
> > I support the full API (excepting email sending, which could come
> > along soon) and the whole project is open source, so you can fork it
> > all you'd like.
> > Please upload some apps, and let me know what your experience is!
> I support the full API (excepting email sending, which could come > along soon) and the whole project is open source, so you can fork it > all you'd like.
Neat! But how are you handling security? I assume that the SDK is restricting things so that it's similar to the real environment, but without the same concern for security (i.e., it is blocking things but assuming you won't try to get around it).
I haven't done much for security... At this point, stack traces will
be visible to anyone, should an error occur in your application.
That's not to say I couldn't. Basically I'm just relying on the App
Engine SDK to be decently sandboxed. The worst thing that could happen
is someone pwns my EC2 instance (which is pretty free of secret keys
and the like). I'm encouraging people not to post sensitive data to
the AppDrop apps for the time being.
If you'd like to look at the code my modified SDK is here:
> > I support the full API (excepting email sending, which could come
> > along soon) and the whole project is open source, so you can fork it
> > all you'd like.
> Neat! But how are you handling security? I assume that the SDK is
> restricting things so that it's similar to the real environment, but
> without the same concern for security (i.e., it is blocking things but
> assuming you won't try to get around it).
I gave a talk last night on Google App Engine and AppDrop - for anyone
who's interested it provides a general outline of App Engine with a
focus on the authentication component of the Python SDK, as well as an
outline of how to do automated sysadmin tasks using a Rails app as a
controller.
> I support the full API (excepting email sending, which could come
> along soon) and the whole project is open source, so you can fork it
> all you'd like.
> Please upload some apps, and let me know what your experience is!
On May 8, 5:07 am, jchris <jch...@gmail.com> wrote:
> I gave a talk last night on Google App Engine andAppDrop- for anyone
> who's interested it provides a general outline of App Engine with a
> focus on the authentication component of the Python SDK, as well as an
> outline of how to do automated sysadmin tasks using a Rails app as a
> controller.
